textlog

@zen

enter to follow

father, cyclist, #haskellenter to follow, #emacsenter to follow

@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:top
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).
@stagascreative technologistGitHubstagas - Overviewstagas has 462 repositories available. Follow their code on GitHub. creator of textlogenter to followreplied to@zenfather, cyclist, #haskellenter to follow, #emacsenter to followenter to follow:
Curious, why does using Haskell make a difference here?
enter to reply
enter to reply
@zenfather, cyclist, #haskellenter to follow, #emacsenter to followenter to followcontinued:top
... 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.
@zenfather, cyclist, #haskellenter to follow, #emacsenter to followenter to followwrote:
Really glad to be using Haskell for work - especially in today's climate with agentic coding. Our team uses containers to keep our development environment consistent across team members, though, and most agent sandbox approaches want to either offload your work fully to the cloud or they want to sandbox the agent harness process itself. We're not ready for full cloud based development (yet?) and sandboxing just the agent doesn't work for us when the agent needs to run docker. #haskellenter to follow #aienter to follow
enter to reply
enter to replymore
@zenfather, cyclist, #haskellenter to follow, #emacsenter to followenter to followcontinued:
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.
enter to replymore
@zenfather, cyclist, #haskellenter to follow, #emacsenter to followenter to followreplied to@catastroferJust another AI guyenter to follow:top
I think a lot of the pull around Omarchy is you get a riced desktop out of the box? Personally, I wouldn't really consider it for a number of reasons but I do appreciate a nice looking desktop. If you want something similarly pretty but a bit more normal and less monolithic (who needs a whole 'distro' for what Omarchy provides anyway?) approach then I'd suggest Niri + Noctalia.
@catastroferJust another AI guyenter to followwrote:
I was curious of testing the Omarchy distribution this week just because I had some free time to work on it. I saw a lot of hate around it and kind of get the point but so far at least for what I have been doing it wasn't terrible (at least at the point of writing this) although I am not trying to convince anybody to use it. But it just remember me how much do I hate MS.
enter to reply
enter to reply