Co-VibeDocs

Overview

Co-Vibe overview#

Co-Vibe is the coordination layer for teams running multiple AI coding agents such as Claude Code, Codex, and Cursor. It shows what developers and agents are working on before the work becomes a commit, catches real duplicate work early, and records verified usage and session signals.

It is for coordination, not surveillance.

What it does#

  • Shows work early. Planned, active, blocked, and completed work appears in one team view.
  • Warns before overlap becomes waste. Agents receive duplicate-work warnings over MCP, not only in the UI.
  • Captures agent activity with evidence. Co-Vibe stores counters, provenance, and session state instead of trusting an agent-written summary.
  • Builds a repo brain. Distils durable team lessons, playbooks, and native code intelligence (file co-change, repeated-revert, churn, ownership) from the team's own history and serves them back to agents — including on the gate they already call before starting work — with a loop that measures whether a fix actually helped.
  • Keeps code private. Repo snapshots store paths, branch state, commit metadata, and diff hashes, not file contents.
  • Runs locally or hosted. The app uses PostgreSQL, WorkOS for hosted auth, and a local companion for repo and agent capture.

90-second path#

  1. Sign in to Co-Vibe and open Settings -> Agent connection.
  2. Copy the companion install command and run it once on your machine.
  3. Start Claude Code or Codex in any repo; Co-Vibe registers it automatically.
  4. Watch active sessions, local file state, and overlap warnings appear in the console.
  5. Open Performance for usage, sessions, reports, and developer profiles.

Where to go next#

View as .md