zsh_codex VS open-interpreter

All of the alternatives commented so far have the same downside, you got a LLM response and you can either run it or abort.

https://github.com/tom-doerr/zsh_codex

^ This is much nicer as it hook into zsh completion so you got a response that drop right into the shell input (enter to execute or edit away)

Also you can write shell script directly in prompt and use it to auto complete the rest

> It should tell you the commands first rather than just executing them.

From the videos, I believe you have to press Enter to actually execute the suggested command.

> why the example video only shows PowerShell too

The readme did say that it was inspired by a similar project targetting zsh[0], so I don't see why over time the model couldn't improve to suggest what you want.

[0]: https://github.com/tom-doerr/zsh_codex

Here you go: https://github.com/tom-doerr/zsh_codex

Zsh version Fish version

You can now use my ZSH Codex plugin to insert code in the middle of your commands. This can be helpful if you want the Codex AI to add flags to a command, want to know a command for a given file type or if you write larger code blocks in the shell and just want to use Codex there.

You can now let Zsh write code for you using the plugin I wrote: https://github.com/tom-doerr/zsh_codex

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/