ๆฅๆฌ่ช่ฉฑ่
ใฏใฉใใใใใใใใ ใใใใใใงๆฅๆฌ่ชใงๆธใ่พผใฟ็ถใใใฎใฏใฉใใชใใ ใใ
I wonder how many Japanese speakers there are. Is it okay to keep posting in Japanese here?
Any conversation
ใใใซใกใฏไธ็
Hello World
ใใใงๆฅๆฌ่ชใงๆธใ่พผใฟ็ถใใใฎใฏใฉใใชใใ ใใ
ใตใคใไฝๆ่
ใฏใใพใใพใฎ่จ่ชใฎ่ฉฑ่
ใไธ็ทใซ่ฉฑใใๅ ด้ขใซใใใๆฐใใใ
I wonder if it's okay to keep posting in Japanese here.
I get the feeling the site creator wants this to be a place where speakers of various languages can talk together.
Error: Provider rejected the request (invalid_request_error, 400): Claude Code 2.1.75 does not support this model; version 2.1.251 or newer is required. Run
'claude update', or update the Claude desktop app, then try again. [request_id: req_011CedKqBRnC6Qr3m6nKEwNN]
Iโm not using Claude Code. This is how you drop the ball.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).
Huge refactor today, moved from sync SQLite to Worker based, touched 88 files, pre- it would have taken a week or so, finished now in ~1:30h. And I wouldnโt have the confidence I have now that it went correct. It went well, though a bug or two might surface, weโll see.
Good work! What motivated the refactor exactly? I'm not familiar at all with Worker
Added
#meta tag โ use it whenever you want to talk about the site itself, and these posts will not show up in all, any or the postโs page. Only those that follow the tag or the person will see these posts in my feed or in post pages. This is to keep the site clear of meta discussions which dominated a lot at this early stage and I think were annoying to many people. So this is the last meta without the #meta tag youโll see unless u follow. Iโll try to tag every post I find.i made it is an open-source version of grammarly that uses chatgpt, grok subscription or even then already local apple intelligence models.
Switched from gpg to age, because pinentry sucks. With age I set both of my Macโs security enclaves + software private key (stored in Passwords.app) + yubikey for hardware backup. Looks good.