Here's my hacked-together, messy, voice-based dev environment:

1. Voice-driven loop with screen-shotting so the LLM in the loop can see what's in my terminal and editor. The prompt varies depending on what I'm trying to drive with this loop.

2. A few tool definitions that give read access to files and URLs.

3. A tool the LLM can send a block of output to that generates keyboard events, so the LLM can drive any editor/terminal.

4. A separate process watching a directory and constantly making LLM-driven git commits. (git autosave).

I have some pieces of this running most of the time. But I'm lazy, and doing other stuff, and I also try to use a variety of editors and tools, to see what's good lately. Which ... no stability, so my hacked-together stuff is always broken.

I don't want to replace @Windsurf / @Cursor / Claude code. A seriously good agent and expert-system dev toolkit is a lot of work.

Here's my hacked-together, messy, voice-based dev environment:

1. Voice-driven loop with screen-shotting so the LLM in the loop can see what's in my terminal and editor. The prompt varies depending on what I'm trying to drive with this loop.

2. A few tool definitions that give read access to files and URLs.

3. A tool the LLM can send a block of output to that generates keyboard events, so the LLM can drive any editor/terminal.

4. A separate process watching a directory and constantly making LLM-driven git commits. (git autosave).

I have some pieces of this running most of the time. But I'm lazy, and doing other stuff, and I also try to use a variety of editors and tools, to see what's good lately. Which ... no stability, so my hacked-together stuff is always broken.

I don't want to replace @Windsurf / @Cursor / Claude code. A seriously good agent and expert-system dev toolkit is a lot of work.