Is it just my phone or is HN down? I haven't been able to access at all today
Any conversation
Iโm using textlog to explore the intersection of and tech, with the goal of building an app that solves a problem in this space. Named , it's word represented as a hex color.
Of all the words there, it is a cocoa-ish color and is an appropriate name for this idea.
Ubuntu telepรญtรฉse a VirtualBoxba rendben megtรถrtรฉnt. Mรกr csak egy รผgynรถkรถt kell bele fogni, รฉs mรกris kรฉsz az "AI torture chamber", ahogy a Futurism รญrja... Mondjuk, elsล kรถrben mรฉg nem รญgy fogalmaznรฉk...
Ubuntu has been successfully installed in VirtualBox. All you need to do is add an agent and you have an "AI torture chamber", as Futurism describes it... Let's just say, I wouldn't put it that way at first...
Putting a slide deck together (outside of work), despite agreeing with Tufte on this matter. Iโll also create a handout that tells the story better than the slides and deliver that, too, but was asked to produce a slide deck, and I think thatโs part of the โeffort theater.โ
Using Beamer for the slides, but not a theme that looks like Beamer because humans have eyes.
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).