cli

The official Claude Code repo is configured use a devcontainer config: https://github.com/anthropics/claude-code You can download the devcontainer CLI and use it to start a Docker container with a working Claude Code install, simple firewall, etc. out of the box. (I believe this is how the VSCode extension works: It uses this repo to bootstrap the devcontainer). Basic instructions: - Install the devcontainer CLI: `https://github.com/devcontainers/cli#install-script` - Clone the Claude Code repo: `https://github.com/anthropics/claude-code` - Navigate to the top-level repo directory and bring up the container: `devcontainer --workspace-folder . up` - Start Claude in the container: `devcontainer exec --workspace-folder . bash -c "exec claude"` P.S. It's all just Docker containers under the hood.

I assume that you are talking about the [devcontainers LCI](https://github.com/devcontainers/cli) when you say "a CLI"?

The devcontainers cli has existed for a while. Definitely not as smooth as using with vscode but it has all the main points. https://github.com/devcontainers/cli

If you are a VSCode hater (like me), you can achieve the same thing using the open-source, Microsoft-built, official devcontainer CLI [0], which is exactly what VSCode uses under the hood. You don't get automatic port forwarding with this tool, which includes SSH Agent forwarding, so you'll likely want to pair this with installing SSH into your devcontainers, or using some other tool that does the job. I built a tool [1] to do the port forwarding part, which I'd like to be more magic like VSCode's but haven't put the effort into doing, since it works for my purposes. Using these, I can SSH into my devserver, use the devcontainer CLI to open a tmux session with iTerm2 Tmux integration, and it feels just like a local window. Combine that with Neovide and remote Neovim over the same channel, and I have a native-feeling dev environment runnin

You still cannot stop, remove or update a Dev container from CLI and there at numerous issues with the rest of the implemented features. [0]: https://github.com/devcontainers/cli?tab=readme-ov-file#cont...

Curious if you tried the devcontainer cli [1] to build your devcontainer.json? DevPod is another implementation of the devcontainer spec, the most used one being the aforementioned devcontainer cli which vscode uses, or supplies, via its integration. If you’re having problems with DevPod while they iron out the kinks you might want to try the devcontainer cli, which can build the images, and run them. 1. https://github.com/devcontainers/cli

Haven't tested it myself, but there's now a cli to decouple devcontainers from VSCode: https://github.com/devcontainers/cli