I had a similar thought, but would I would like to maintain control what the LLM has access to. It would be difficult to prevent things you might temporarily ha

I had a similar thought, but would I would like to maintain control what the LLM has access to. It would be difficult to prevent things you might temporarily have hardcoded or generally do not want to expose. I started working on something for this purpose called j-dev [0]. It started as a fork off smol-dev [1] which basically gets GPT to write your entire project from scratch. And then you would have to iterate the prompt to nuke everything and re-write everything, filling in increasingly complicated statements like "oh except in this function make sure you return a promise" j-dev is a CLI where it gives a prompt similar to the one in the parent article [2]. You start with a prompt and the CLI fills in the directory contents (excluding gitignore). Then it requests access to the files it thinks it wants. And then it can edit, delete or add files or ask for followup based on your response. It does stuff like make sure the file exists, show you a git diff of changes, respond if the LLM is not following the system prompt, etc. It also addresses the problem that a lot of these tools eat up way too many tokens so a single prompt to something like smol-dev would eat up a few dollars on every iterations. It's still very much a work in progress and i'll prob do a show hn next week but I would love some feedback [0] https://github.com/breeko/j-dev https://github.com/breeko/j-dev [1] https://github.com/smol-ai/developer https://github.com/smol-ai/developer [2] https://github.com/breeko/j-dev/blob/master/src/prompts/system.ts https://github.com/breeko/j-dev/blob/master/src/prompts/syst...