VibeCraft

What Is VibeCraft?

VibeCraft reframes multi-agent coding as a real-time strategy game. You get an infinite pannable canvas where agents, project folders, terminals, and browser panels are draggable entities you arrange spatially.

The RTS metaphor is literal: Hero (command center), Agents (Claude Code or Codex units), Folders (project entities), and status indicators like unit health bars — gray for idle, green for online, red for error. Built-in git worktree actions, embedded browser panels, and a context-aware HUD round out the workspace. VibeCraft is self-hosted on Mac, Windows, and Linux with no cloud dependency.

Typical usage: spawn two Claude Code agents, attach each to a different project folder or worktree, run tasks simultaneously, and keep both terminals visible on one canvas without tab-switching.

Where Ravi Fits

VibeCraft solves the visibility and coordination problem for parallel agents. Ravi solves the identity problem that emerges once you actually run them.

Per-agent credential isolation. Two agents, two projects, two sets of service credentials. Ravi’s password vault lets each VibeCraft agent pull project-scoped credentials on demand via MCP. No shared .env files across worktrees means no credential collisions and no accidental cross-contamination between agents working on different services.

Agent identity for service signups. Agents frequently need to create accounts mid-task — a Stripe sandbox, a SendGrid trial, a SaaS API key. Ravi provisions a unique email address and phone number per agent, solving the “what identity do I use?” problem at the point of need. Two agents can simultaneously hit different services without routing through the same developer account.

TOTP and 2FA without human interruption. VibeCraft’s core value is reducing human interruptions while keeping agents observable. But 2FA breaks that loop. Ravi’s TOTP and SMS verification lets an agent complete authentication flows autonomously — the developer never needs to tab-switch to enter a code. The canvas stays the single pane of glass.

Setup Guide

Prerequisites

• VibeCraft installed (see the VibeCraft repo for installation)
• A Ravi identity provisioned via the Ravi dashboard
• The Ravi MCP server running (for in-agent credential access)

Inject Ravi credentials into a VibeCraft workspace

When spawning an agent entity in VibeCraft, set environment variables from Ravi before the agent process starts. In your workspace configuration, add a setup step:

export RAVI_EMAIL=$(ravi identity email)
export RAVI_PHONE=$(ravi identity phone)
export RAVI_API_KEY=$(ravi secrets get RAVI_API_KEY)

These variables are then available to the agent running in that terminal pane.

Use Ravi MCP for in-agent credential access

Add the Ravi MCP server to your agent’s MCP configuration so it can retrieve credentials during task execution:

{
  "mcpServers": {
    "ravi": {
      "command": "ravi",
      "args": ["mcp", "serve"]
    }
  }
}

With this in place, agents running in VibeCraft can call ravi_secrets_get or ravi_passwords_get inline — pulling credentials at the moment they’re needed rather than requiring them to be pre-seeded.

Handle 2FA autonomously

When an agent hits an SMS verification prompt, it can poll Ravi’s SMS inbox via MCP:

ravi_inbox_sms → find unread from verification sender
ravi_read_sms → extract the OTP code

The agent completes the flow without any human intervention, and VibeCraft’s canvas reflects the continued progress rather than a stall.

Why This Matters

VibeCraft makes parallel agent work visible. Ravi makes it safe. Running agents in parallel without isolated identities means they share credentials, share email addresses, and share blame when something goes wrong. Ravi gives each canvas entity — each Hero unit, each Agent — its own accountable identity. The visual metaphor becomes literal: every unit on your canvas is a distinct actor with a distinct presence in the world.