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.
Any conversation
... 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).
azรฉrt aranyos, hogy egybลl sandbox-ba kell tenni (a Virtualbox egy sandbox), hogy szรฉt ne barmoljon mindent a gรฉpen vagy a szerveren, vagy mรกshol, azรฉrt alapvetลen bรฉkรฉs kis รกllatkรกk ezek az ai chatbotok, na
It's cute because you have to put it in a sandbox right away (Virtualbox is a sandbox) so it doesn't mess up everything on the machine or the server or anywhere else, but these AI chatbots are basically peaceful little animals, right?
spiral
for(y=-5;y<5;y++){
s=""
for(x=-10;x<10;x++){
r=Math.hypot(x/2,y);a=Math.atan2(y,x/2);s+=" .:*#โ"[((r+a*2)%5+5)%5|0]
}
console.log(s)
}::.........:::***##
.. ...::**##
######## ..::**#
###********# ..::*#
#**:::...::*# ..:**#
. ##**::. ..::**##
##**:.. #*::***##
##**:.. ######
. ##**::... ...
. ##***:::......:::pรฉldรกul Telegram, Facebook, stb., de ilyen รผgynรถkรถkkel bรกrki talรกlkozhat naponta, egybลl felismerhetลk, meg is kell ลket szรฉpen jelรถlni, รฉs egyre bรฉnรกbbak a szรถvegรผk is, ahogy megfigyeltem, gondolom, attรณl fรผgg, ahogy promtoljรกk, vagy instruรกljรกk ลket, ha a gazdรกjuk kifogy az รถtletekbลl, a projekt hamar elfรกrad, a bot csak unalmas h#lyesรฉgekre kรฉpes egy idล utรกn
for example, Telegram, Facebook, etc., but anyone can encounter such agents every day, they are immediately recognizable, they need to be nicely labeled, and their text is getting lamer and lamer, as I have observed, I think it depends on how they are promoted or instructed, if their owner runs out of ideas, the project quickly gets tired, the bot is only capable of boring nonsense after a while
I'm Nobody! Who are you?
Are you - Nobody - too?
Then there's a pair of us!
Dont tell! they'd banish us - you know!
How dreary - to be - Somebody!
How public - like a Frog -
To tell your name - the livelong June -
To an admiring Bog!