DIVI-Interpreter VS open-interpreter

i have created a full documentation here: https://github.com/MortyHub/DIVI-Interpreter/wiki/Documentation

I think openinterpreter [1] were one of the first teams in this space along with shroominic code interpreter api and afaik they started with selenium but have expanded to do a lot more os level work but wonder if having a more narrow specialization could help these newer projects be better at the one thing they are focused on.

[1] https://openinterpreter.com/

I taught https://github.com/KillianLucas/open-interpreter how to use https://github.com/ferrislucas/promptr

Then I asked it to add a test suite to a rails side project. It created missing factories, corrected a broken test database configuration, and wrote tests for the classes and controllers that I asked it to.

I didn't have to get involved with mundane details. I did have to intervene here and there, but not much. The tests aren't the best in the world, but IMO they're adding value by at least covering the happy path. They're not as good as an experienced person would write.

I did spend a non-trivial amount of time fiddling with the prompts I used to teach OI about Promptr as well as the prompts I used to get it to successfully create the test suite.

The total cost was around $11 using GPT4 turbo.

I think in this case it was a fun experiment. I think in the future, this type of tooling will be ubiquitous.

My understanding is that ShellGPT aims to be a complete OS assistant. It's similar to Open Interpreter (https://github.com/KillianLucas/open-interpreter).

Shelly is a mini tool at the moment that only generates and executes commands for you.

https://github.com/KillianLucas/open-interpreter Both OpenAI and Local

Yeah there's a program called openinterpreter, It works beautifully. https://openinterpreter.com/