Hacker News .hnnew | past | comments | ask | show | jobs | submitlogin

I personally won't allow full control for a long time.

On the other hand LLMs have been a very good tool to build bespoke tools (scripts, small CLI apps) that I can allow them to use. I prefer the constraints without having to think about sandboxing all of it, I design the tools for my workflow/needs, and make them available for the LLM when needed.

It's been a great middle ground, and actually very simple to do with AI-assisted code.

I don't "vibecode" the tools though, I still like to be in the loop acting more as a designer/reviewer of these tools, and let the LLM be the code writer.



But does the agent have access to a whole computer to write those tools?

Couldn't it write them in a web based dev environment?


No, it doesn't, I only run agents in a dedicated development environment (somewhat sandboxed in the file system) but that's how I've used them since the beginning, I don't want it to be accessing my file system as a whole, I only need it to look at code.

Don't think a web-based dev environment would be enough for my use case, I point agents to look into example code from other projects in that environment to use as as bootstraps for other tools.


Why can't that "dedicated development environment" be a cloud VM with a web interface, a GitHub codespace for example?

You could put the example code on the filesystem of that VM too.


It could be…




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: