Still in Quebec City, which has a pretty sizable street population once you come down from the hill where the tour groups go. We had to basically step over some guys sharing a glass pipe on the only stairs up the hill yesterday; I have teenagers so this bothered me.
Later, my youngest and I were talking and he says "why don't the police do something about that?"
Any conversation
Added it as a company on LinkedIn so it must be 'live' now. Cheltenham-od.uk
i always have to resist dream futures that are way out of my league. no, Orit no! you can't be a priest your a girl!!!! noo!!! you can't be a cardinal either, stop!!
did they silently decrease the subscription limits on codex? (in addition to reintroducing the 5h limit?) subscription models suck so bad when they can just change the terms and make the product shittier.
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).
@fastidiousprofilefollow
"Beware those that would deny you access to information, for in their heart they dream themselves your master." — Sid Meyersreplied to:
"Beware those that would deny you access to information, for in their heart they dream themselves your master." — Sid Meyersreplied to:Just check, and top off as needed, the tyres pressure. Run it for a few miles. If it doesn’t go away, then take that trip.
replied to@fastidiousprofilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." — Sid Meyers:
"Beware those that would deny you access to information, for in their heart they dream themselves your master." — Sid Meyers:No gas station near me has nitrogen so it had to be Costco. I topped off air and also filled gas while I was there. It’s only 5 miles from me, so overall not bad.