Feather to paper
that's moon inked for you --
a greeting from somewhere.
It isn't for you.
But it will be for you.
Any conversation
โฆ
what?
@fastidiousprofilefollow
"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyerswrote:
"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyerswrote:There is someone absolutely rotten and fetid in this airplane. Every 10 minutes. Dear Spaghetti Monster!
Drew a comic of vulpes inculta and my oc, I love SO MUCH!!
ibb.co/B2x8dq9n
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).
everytime i see projects like this, i think that a rss implementation it wolud be so cool. Although iknow that there is not that much rss lover out there haha
anything you'd like to talk about
Interface looks sleek. The idea of text based messaging is quite interesting in the age photos and videos based heavy apps.
haha, yes. it's quiet on here though!
Thatโs also the point isnโt it? The people who like this place doesnโt like it too busy. So for them (us?) it will be a nice place to hang out as long as it stay uncommercial and low-key. But to be prosperous and interesting to the creator, it need to grow. ๐คทโโ๏ธ
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...