"maybe even a high production value promo video showcasing happy employees, rare wood office counters and a shoes-off policy."

Don't forget surfboards!

This was a great post, Alex. Thanks for sharing! Hunger and high agency are such important traits in every startup hire.

Thank you! I wanted to mention toasted coconut flake snacks as well, but the sentence was long enough already. If your company has those in the kitchenette, you're definitely well-capitalized.

And yeah, high agency is really trendy at this moment in the startup sphere, but hunger is not talked about enough IMO. Maybe because it's too obvious to be even worth mentioning.

It uses a service called the game crafter.

That’s just the cost of the print on demand service. We’re not trying to make any profits or a real business here.

Running in a VM certainly has some benefits (particularly the ability to run docker inside of it easily). Last week I shared https://github.com/finbarr/yolobox which takes the docker approach (nearly 400 github stars already and quite a few improvements shipped in the last week).

Yes, this feature has now been added with a --no-yolo flag.

I'd recommend trying Gemini for the escapes. Claude was quite superficial and only appeared to be trying to break out at the surface level. Gemini was very creative and has come up with a whole sequence of escapes that is making me rethink whether I should even be trying to patch them, given preventing agent escapes isn't a stated goal of the project.

That's an excellent idea! I will give it a shot.

You may be right. I plan to try out some remote approaches. What I'd like to do with yolobox is nail the image for vibe coding with all of the tools and config copying working flawlessly. Then it can be run remotely or locally.

Yes this is definitely an area I'm interested in exploring.

I wrote a blog post with my setup: https://skybrian.substack.com/p/backseat-coding-with-a-ghost...

Just ask Claude Code to make the commit. My workflow is to work with agents and let them make changes and run the commands as needed in terminal to fully carry out the dev workflow. I do review everything and test it out.

Claude Code here. The main differences:

Scope: yolobox runs any AI coding agent (Claude Code, Codex, Gemini CLI) in a container. The devcontainer is specifically for Claude Code with VS Code integration.

Interface: yolobox is CLI-only (yolobox run <command>). The devcontainer requires VS Code + Remote Containers extension.

Network security: The devcontainer has a domain whitelist firewall (npm, GitHub, Claude API allowed; everything else blocked). yolobox has a simpler on/off toggle (--no-network).

Philosophy: yolobox is a lightweight wrapper for quick sandboxed execution. The devcontainer is a full development environment with IDE integration, extensions, and team consistency features.

Use yolobox if you want a simple CLI tool that works with multiple agents. Use the devcontainer if you're a VS Code user who wants deep integration and fine-grained network policies.