๐๐ฎ๐ฐ ๐ ๐๐ฎ๐ฐ ๐ช๐ฏ ยท๐๐ฎ๐ฆ๐๐ฆ๐ ๐๐ฆ๐๐ฉ๐ ๐๐ฆ๐ ๐ข๐ฐ๐๐ง๐ฏ๐: ๐ฃ๐จ๐ ๐ฉ ๐๐ซ๐ค ยท๐ฆ๐๐๐ค๐ฆ๐ ๐ฏ ๐ฉ ๐๐ฒ (๐ฎ๐จ๐๐ฆ๐) ๐๐จ๐๐๐ผ๐๐ฑ, ๐ฏ๐ฌ ๐ ๐๐ต ๐จ ๐๐ฐ๐ ๐ฎ๐ด๐๐. ๐ค๐ณ๐๐ค๐ฐ ๐ฏ ๐๐ท๐๐ฐ ๐ฆ๐ฏ ๐๐ฆ๐ ๐ท๐๐ณ๐ฅ๐ฏ๐ฉ๐ค ๐ข๐จ๐๐ผ.
Three for three on British dishes this weekend: had a full English and a pie (rabbit) yesterday, now to do a beef roast. Lovely and cozy in this autumnal weather.
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).
I'm doing experiments with short attention-span students and code. Starting with python, and, oddly, now working in BASIC. As a C programmer of 40+ years, I find this aesthetically and pedagogically displeasing, but I am delighted to see them getting fully absorbed in writing
130 PRINT "You have been eaten by a bear!" : GOTO 900. Yes there is spaghetti, but it's their spaghetti and they seem to take delight in debugging it. Python will come later.