Hi everyone! I just found this site, seems to be just my speed!
Any conversation
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.
... 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.
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.... in the end, this seems to work but I haven't lived with it for long.
There are still some quality of life issues to work out, but I think it'll work out.
At this point, I've removed all coding agents from my host - and that's nice.
Curious, why does using Haskell make a difference here?
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).
WezTerm for local and remote multiplexing really is the ideal experience - it's so much better than using zellij, tmux, zmx, and friends.. I don't think they pitch this feature hard enough on their site.
I think the in-terminal multiplexers have their place - e.g. if you need to access from mobile (no WezTerm there) or on machines where you simply don't want to install WezTerm for some reason. WezTermrm could probably eliminate that last one by packaging just the mux server.
How do you define slop in relation to ? For me, it is how quickly you get to an unmaintainable state- the acceleration into something that becomes difficult to work. I talk more about it here: hellodavid.dev/blog/slop
โโโโโโโโโโโโโโโโโโโโ โโโโโโโโโโโโ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โโโ โโโโโโ โโโโโโ โโโ
โโโ โโโโโโ โโโโโโ โโโ
โโโ โโโโโโโโโโโโ โโโ โโโ
โโโ โโโโโโโโโโโ โโโ โโโ
I truly love the experience of using apps with rich, deeply interactive, beautifully animated, gorgeous user interfaces.
Then I see a beautiful text-based interface and something about it feels so natural, so inevitable, so perfectly clear, and I'm instantly captivated by its simplicity and clarity.
Hypertext is fascinating.
a szerveren lรฉvล cookie adatokat รฉs egyรฉb nyomkรถvetล sz@rokat is a Google kezeli, รฉn nem igazรกn szoktam ezekbลl lรกtni semmit, se ip-t, se semmit, a Google inkรกbb keresลmotor, mint mestersรฉges intelligencia alkalmazรกs, de ma mรกr hibrid technolรณgiรกval dolgozik minden MI รฉs keresล
Google also manages the cookie data and other tracking s@rs on the server, I don't really see anything from these, no IP, nothing, Google is more of a search engine than an artificial intelligence application, but today all AI and search engines work with hybrid technology