withvibe
Sign in
Docs

Welcome to withvibe

withvibe is a platform for shared AI environments. Anyone on a team — stakeholder, PM, dev, QA, sales — can spin up an isolated, AI-powered env and build a feature together. Devs stay in control. Specialist agents review the result before it ships.

Self-host first
These docs are written for teams running withvibe on their own infrastructure. A managed cloud is on the roadmap — until then, the entire system runs locally with Docker.

Find your path

Pick a starting point based on what you're here to do:

Quickstart
Spin up your first shared env in 5 minutes.
Self-host withvibe
Run the full stack on your own infra with Docker compose.
Concepts
Workspaces, envs, shared sessions, and the agent gate.
CLI reference
Every flag of the withvibe CLI.

What withvibe is, in one paragraph

A withvibe deployment runs three services: a web app where teammates create and join envs, an API that orchestrates Docker, Git, and the AI agent, and Postgresfor metadata. When someone clicks “new env,” the API spawns a fresh isolated container on the host Docker daemon, clones the repo into it, starts a shared Claude Agent SDK session, and streams the chat + terminal back to everyone invited. When the team is happy, an agent gate (security, code review, tests, policy) runs before the changes merge to main.

What this is not

  • Not a single-player AI editor. withvibe is built around a session that multiple humans share with one AI.
  • Not a replacement for code review. Devs still review and merge. The agent gate is a safety net, not the only gate.
  • Not a hosting platform. Envs are dev/preview environments, not production runtime. Your existing CI/CD ships the merged code.

Help & community

  • GitHub — source code, issues, releases
  • GitHub Discussions — questions, recipes, show-and-tell
  • FAQ — the questions people ask most often
Next Quickstart