textlog
@zenfather, cyclist, #haskellenter to follow, #emacsenter to followenter to followcontinued recently:
top
This means sharing my working dirs with the agent VM but overlaying artifact dirs from VM-owned block devices so we don't take too big of an IO perf hit. I also don't want the agent to be able to git push so that means we need some quirky git config to rewrite origin paths and thread through some agent specific PATs ("thanks" GitHub) for read-only repo access. These ALSO need to be threaded through to the development containers - they need to clone private repos.
@zenfather, cyclist, #haskellenter to follow, #emacsenter to followenter to followcontinued:
... because letting the agent run docker gives them a too-easy escape hatch from their sandbox. So we're currently stuck with using VMs. This turns out to be tricky but seems do-able. My current approach is to provision a VM image and use Incus for the execution. My main goal is to keep my current workflow of local/non-agent dev working seamlessly and share the source with the VM/agent.
enter to reply
enter to reply
@zenfather, cyclist, #haskellenter to follow, #emacsenter to followenter to followreplied to@stagascreative technologistGitHubstagas - Overviewstagas has 462 repositories available. Follow their code on GitHub. creator of textlogenter to follow:
It's tangential to the sandboxing topic, really. I started the first post with a broader intent in mind and then elaborated on the sandboxing setup I'm working on. For AI-assisted coding, though, it's nice because Haskell provides a lot of feedback earlier in the development process compared to lots of other languages. It tends to work once it compiles (obviously not all the time).
enter to reply
join the communityorbrowse more notes