VibePod — Containerized AI Coding Agent Runner

What does this agent do, and when should you use it?

VibePod is a unified CLI (invoked as vp) for launching AI coding agents inside isolated Docker or Podman containers. The execution model is deliberately zero-config: vp run <agent> resolves the agent to a default image under the vibepod Docker Hub namespace (for example vibepod/claude:latest), starts it in a container, and forwards anything after -- to the agent process itself. Alongside vp run there are vp stop, vp list, vp config init/show/path, and vp version for lifecycle and configuration management. Per-project customization is expressed as a FROM-less Dockerfile fragment committed under .vibepod/overlay/, which VibePod builds into a cached, content-addressed layer on top of the agent's base image. While agents run, VibePod collects local metrics and HTTP traffic and exposes them through a dashboard container started with vp logs start, showing per-agent usage, traffic and Claude token metrics, plus side-by-side agent comparison. Everything stays on the local machine, and --acp turns vp into an Agent Client Protocol adapter so containerized agents appear directly in editors such as Zed.

VibePod parses the subcommand and agent name, separating its own flags from agent arguments (use -- before agent flags), then maps the agent to a default image or to an override supplied via VP_IMAGE_<AGENT> environment variables. It starts an isolated container with Docker or Podman and runs the agent process inside it. --ikwid appends each agent's auto-approval flag where supported (claude's --dangerously-skip-permissions, gemini's --approval-mode=yolo, copilot's --yolo, and so on), while --acp exposes the containerized agent as an Agent Client Protocol server for editor integration. Project-specific dependencies are added by committing a FROM-less Dockerfile fragment under .vibepod/overlay/, which is auto-built into a cached, content-addressed image layer. During execution VibePod records local metrics and HTTP traffic; vp logs start/stop/status manages the dashboard container (default image vibepod/datasette:latest), which renders per-agent traffic, usage over time, Claude token metrics, and agent-to-agent comparisons. vp skills add installs reusable prompt recipes, and the vp config commands manage configuration files and allowed directories.

1. A platform team wants several engineers to try Claude, Codex and Gemini side by side without each person installing and configuring a different agent toolchain.
2. A developer under security or compliance constraints needs agents confined to a container with controlled filesystem and network access rather than running directly on the host.
3. Someone deciding which agent is worth paying for opens vp logs start and compares token consumption and request traffic across agents in the local dashboard.
4. A Zed user wants the isolated agent inside the editor's AI panel, achieved by registering vp run <agent> --acp as a custom agent server.
5. A project needs extra tooling inside the agent image; instead of maintaining a fork, the team commits a Dockerfile fragment under .vibepod/overlay/ and lets VibePod build a cached per-project layer.
6. A Podman user on Linux wants the same agent launching workflow that Docker users get, without switching container runtimes.

How do you install or deploy this agent?

VibePod is published on PyPI, Homebrew, and conda-forge. Pick one:

pip install vibepod

brew install vibepod/vibepod/vibepod

conda install -c conda-forge vibepod
# or
mamba install -c conda-forge vibepod
pixi global install vibepod

A working Docker or Podman installation is required on the host; the first run pulls the agent image from the vibepod namespace on Docker Hub.

How do you use this agent?

Basic invocation:

vp run <agent>
# e.g.
vp run claude
vp run codex
vp run vibe   # alias of devstral

Pass agent flags after -- so VibePod does not parse them as its own options:

vp run <agent> -- <agent-args>

Skip approval prompts where the agent supports it:

vp run claude --ikwid

Editor integration (Zed example; run vp config allow-dir /path/to/project first, since the editor's stdin is a pipe and the interactive prompt cannot run):

{
  "agent_servers": {
    "VibePod Claude": {
      "type": "custom",
      "command": "vp",
      "args": ["run", "claude", "--acp"],
      "env": {}
    }
  }
}

Local analytics dashboard:

vp logs start
vp logs status
vp logs stop

Override a default image:

VP_IMAGE_CLAUDE=vibepod/claude:latest vp run claude

What are this agent's strengths and limitations?

How does this agent compare with similar options?

Key facts side by side with the most closely related agents.

How does FollowAgents rate this agent?

Recent releases

Latest entries from the project's GitHub Releases. Notes are quoted from upstream as written, not rewritten or tested by FollowAgents.

1. 0.24.0 2026-09-25
   Release notes excerpt

   What's Changed * Custom providers by @nezhar in https://github.com/VibePod/vibepod-cli/pull/185 * Add vp skills cache clear command by @nezhar in https://github.com/VibePod/vibepod-cli/pull/186 * Provider import export by @nezhar in https://github.com/VibePod/vibepod-cli/pull/187 * Mount custom volumes from agents.<agent>.volumes and vp run -v/--volume by @nezhar in https://github.com/VibePod/vibepod-cli/pull/188 * Send a VibePod User-Agent for model discovery and provider file fetches by @nezhar in https://github.com/VibePod/vibepod-cli/pull/190 …

   View on GitHub ↗
2. 0.23.1 2026-09-17
   Release notes excerpt

   What's Changed * Add example overlay for pi agent to use mcp adapter by @nezhar in https://github.com/VibePod/vibepod-cli/pull/180 * Run skills engine through the Docker SDK instead of the docker binary by @nezhar in https://github.com/VibePod/vibepod-cli/pull/177 * chore: bump version to 0.23.1 by @nezhar in https://github.com/VibePod/vibepod-cli/pull/182 Full Changelog: https://github.com/VibePod/vibepod-cli/compare/0.23.0...0.23.1

   View on GitHub ↗
3. 0.22.0 2026-09-04
   Release notes excerpt

   What's Changed * docs: add DeepSeek Harness screenshot to README and agent docs by @nezhar in https://github.com/VibePod/vibepod-cli/pull/160 * Log profile name on sessions by @nezhar in https://github.com/VibePod/vibepod-cli/pull/163 * chore: bump version to 0.22.0 by @nezhar in https://github.com/VibePod/vibepod-cli/pull/167 Full Changelog: https://github.com/VibePod/vibepod-cli/compare/0.21.0...0.22.0

   View on GitHub ↗

FAQ