Rivets
Documentation

Introduction

Rivets is a multiplayer orchestrator for coding agents. You connect your own machines as workers, send tasks to the Claude Code and Codex CLIs running on them, and watch and steer each run together with your team in real time. When the work is done, you open the pull request, follow its checks, and merge it from the same place.

How it works

  • Workers run the agents. A worker is a machine you own running the rivets CLI, or the Mac app with its bundled worker. It connects outbound to Rivets, so it needs no open ports.
  • Tasks are isolated workspaces. Every task gets its own branch and git worktree on a worker. An agent works there, and Rivets uploads the changes as it goes.
  • Everyone sees the same stream. Agent output streams to every client live. Any member with access can steer the agent, queue follow-ups, and review the diff while it is still being written.
  • Integrations bring work in and send results out. Rivets opens and merges pull requests through its GitHub App, picks up Linear issues delegated to it, answers in Slack, and exposes its task surface to external agents over MCP.
  • Rivets has no app-side AI. Every model call runs on a worker with your own Claude Code or Codex login. Inference is billed to your subscription, never to Rivets.

What you need

  • A worker machine. macOS, Linux, or Windows for the standalone worker. The Mac app requires macOS 15 or later and includes a worker.
  • An agent CLI. Claude Code, Codex, or both, installed and signed in on the worker.
  • git 2.40 or later on the worker.
  • GitHub repositories connected through the Rivets GitHub App. Credential-free and file:// remotes also work, without pull requests.

Run rivets doctor on a machine to check these prerequisites. See Connect a worker.

Where to go next

Type to search the docs.