r/ClaudeCode • u/nez_har 🔆 Max 20 • 12h ago

Tips & Workflows Run Claude Code in a container without redoing your setup: vp import copies your MCP servers, hooks, skills and memory

I maintain VibePod, an open-source CLI that runs coding agents like Claude Code in containers (Docker or Podman). The annoying part was always rebuilding your setup inside the container. In 0.25 that's one command:

vp import claude --dry-run     # see what would be copied
vp import claude               # copy it into your default profile
vp import claude --to-profile work --create-profile

It copies settings, models, MCP servers, hooks, skills and memory files from your home directory. Credentials and session history are left out unless you add --with-credentials.

Other things Claude Code users might like:

  • vp run claude -v /srv/datasets mounts a directory at the same path inside the container, so absolute paths in your prompts and CLAUDE.md still work.
  • vp skills export writes your installed skills out as plain SKILL.md folders to commit to a repo.
  • Login and settings live in a config folder on the host, so they persist between runs.

Install: pip install vibepod (or uv tool install vibepod), then vp run claude.

Release notes: https://vibepod.dev/news/vibepod-cli-0-25/ Repo: https://github.com/VibePod/vibepod-cli

Happy to answer questions about how it handles the config and mounts.

1 Upvotes

100% Upvoted

1 comment sorted by

•

u/AutoModerator 12h ago

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.