Ravi

vibe-kanban

vibe-kanban

vibe-kanban (by BloopAI) is a full-stack kanban and agent workspace system. You plan work as issues on a board, then spin up isolated workspaces where coding agents execute — each workspace gets its own git branch, terminal, and dev server. It supports 10+ agents out of the box: Claude Code, Codex, Gemini CLI, GitHub Copilot, Amp, Cursor, OpenCode, Droid, CCR, and Qwen Code. One command gets you started: npx vibe-kanban. Self-hosting via Docker is supported for teams.

GitHub: https://github.com/BloopAI/vibe-kanban

How vibe-kanban Works

vibe-kanban structures agent work around a human-in-the-loop kanban flow:

  • Issue planning — humans define tasks with priority and assignment on a kanban board
  • Isolated workspaces — each task runs in a dedicated workspace with its own git branch, terminal, and dev server
  • Agent execution — agents pick up issues, execute in their workspace, and surface a diff for inline human review
  • PR automation — after human approval, the agent opens a PR with an AI-generated description
  • Built-in browser — agents can preview running apps with devtools directly in the UI
  • Cloud and team support — relay/tunnel mode for remote server deployments and multi-user workflows

vibe-kanban is essentially a lightweight product management and CI loop designed around agent-human handoffs. The human stays in control of what gets shipped; the agent handles execution.

Where Ravi Fits

The gap vibe-kanban doesn’t address is what happens when agents need to interact with the outside world — not just write code, but sign up for services, receive verification codes, store credentials, and manage API keys. Three concrete integration points:

Per-workspace agent identity

Each workspace is an isolated agent session. Ravi can provision a unique email address and phone number per workspace, so agents can register for external services — npm packages requiring email confirmation, SaaS APIs needing SMS verification, cloud providers with account setup flows — without sharing credentials across workspaces or exposing developer contact information.

Workspace closes. Identity persists in Ravi, scoped to that project. No credential mixing between agent runs.

Encrypted secrets vault for workspace agents

Agents running in vibe-kanban workspaces frequently need API keys: Stripe, GitHub tokens, cloud providers, third-party SaaS. Without a vault, these end up in plaintext .env files that risk accidental commits or persist after the workspace is torn down.

Ravi’s encrypted secrets store gives agents a clean pull-at-runtime pattern. The agent fetches the key when it needs it, uses it, and the credential never touches the workspace filesystem. When the workspace is deleted, nothing sensitive is left behind.

Team relay via Ravi email

For async review workflows — especially in relay/tunnel mode where the human reviewer isn’t watching the UI — Ravi can close the loop via email. When an agent’s diff is ready for review, a Ravi email goes to the reviewer. When review comments come back, Ravi routes them to the agent. The agent makes changes, pushes, and the cycle continues without anyone sitting at a keyboard waiting.

Integration Pattern

The recommended integration adds a Ravi Identity setting at the workspace level.

When a new workspace is created in vibe-kanban, it queries the Ravi API to provision a scoped email and phone for that workspace. Agent tasks that require external signups or verifications use those credentials. API keys and tokens are pulled from Ravi’s secrets store at task execution time rather than baked into workspace env files.

# Install the Ravi MCP server
npm install @ravi/mcp-server

# Configure vibe-kanban to use Ravi for workspace identity
# In your vibe-kanban workspace config:
{
  "identityProvider": "ravi",
  "raviProjectId": "your-project-id",
  "autoProvisionEmail": true,
  "autoProvisionPhone": true
}

At workspace creation, vibe-kanban provisions a Ravi identity and stores the credentials scoped to that workspace. Tasks that need external services get the provisioned contact details. Secrets are fetched from Ravi at runtime and never written to the workspace filesystem.

Why This Matters

vibe-kanban has strong ecosystem traction — 10+ agent integrations, active community, and cloud/team use cases already on the roadmap. The architecture is built for human-agent handoffs, which is exactly where identity gaps surface: agents that need to register for services, receive verification codes, and manage secrets across isolated workspaces.

Without Ravi, vibe-kanban agents are limited to working inside a repo. With Ravi, they can operate as accountable entities on real internet services — sign up, verify, deploy, integrate — while keeping credentials scoped and auditable at the workspace level.

The identity layer is the missing piece for agents that do more than write code. vibe-kanban provides the orchestration surface; Ravi provides the credentials infrastructure that makes autonomous execution safe to run in production.