
Why I Run My Coding Agent Inside a Devcontainer
I limit what Claude Code can touch to the inside of a container, so I can use auto mode without worrying, and I use named volumes to decide which environment reads and which one writes.
Tag archive

I limit what Claude Code can touch to the inside of a container, so I can use auto mode without worrying, and I use named volumes to decide which environment reads and which one writes.
Goal Keep Claude Code's account/session login (~/.claude.json) alive across devcontainer...
The problem Every frontend and full-stack developer has typed nvm install or nvm use into...
This post is targeted devcontainer users not running the containers as root! "remoteUser":...
I often work in repositories with multiple Dev Container configurations. The usual command gets...
How to share your ~/.ssh/config with devcontainers The purpose is to enable using git with...
Ralph is a deceptively simple pattern: put one prompt in a while loop and let a coding agent hammer...

This goal of this tutorial is to provide a way to easily be test driven with spark on your local...
Since I’ve become increasingly unsure about the current state of NUKE Build, I’m experimenting with...
Learn how to develop and publish custom Dev Container Features for VS Code, using the Amazon Q CLI feature as a practical example. Includes forking, feature creation, publishing to GHCR, and submitting to the official features index.
About The concrete implementation was made on MacOS, but it should be quite easy to alter...

Even though Cargo makes it a breeze to work with different toolchains and dependencies, having an...