Pi 1.0 and Gondolin: Codemode, Pi Durable, and a Clean 3-Tier Sandbox
How I run Pi 1.0.4 on the host, experiment with Durable sessions, and isolate regular Pi in Gondolin without per-tool wrappers.
Development#pi#gondolin#security
From a 6.2GB baked toolchain image to boot-time installs from repo lockfiles
I removed the per-repo toolchain from my Gondolin dev VM image and made each repo install its own tools at boot from its mise.lock.
Development#gondolin#mise#sandboxingAWS auth in a Gondolin VM: why SigV4 breaks the secrets bridge
The Gondolin bridge substitutes placeholders in request headers, but the AWS SDK signs the request over the placeholder value. The substitution happens too late and every call returns SignatureDoesNotMatch. The fix is to mount the host's ~/.aws/ read-only instead.
Development#gondolin#aws#sigv4Gondolin sandboxing for AI coding agents: two tiers from tool-only to full clean room
A two-command setup that runs the pi coding agent with either tool-only filesystem sandboxing or full clean-room isolation, each tier matching a different threat model.
Development#pi#gondolin#securitypi crashed inside the Gondolin sandbox: the Bun vs Node runtime mismatch
A Gondolin-sandboxed pi session crashed on socket close because mise ships pi as a Bun binary while the Gondolin SDK targets Node; installing pi via npm under mise-managed Node fixed it.
Development#pi#bun#node