Rivets

Break free from your IDE.

Rivets runs Claude Code and Codex on your own machines and streams every session to your team in real time. Start work from Linear, Slack, GitHub or your phone. Anyone can watch, and anyone can step in.

  • Runs on your machines
  • Your Claude and Codex subscriptions
The Rivets Mac app: a task transcript where a teammate's message is attributed by name, the agent is running with a tool-call summary, two teammates are present, and the Changes panel lists five edited files with line counts.

Start and steer work from the tools you already have open

  • Linear
  • GitHub
  • Slack
  • macOS
  • iPhone and iPad
  • Web
  • MCP

Coding agents are still single-player.

They write good code. But they run in one terminal, on one machine, for one person. Everyone else finds out when a pull request shows up.

01

One person, one terminal.

The session lives in whoever started it. Teammates cannot see what the agent is doing, and nobody else can step in when it drifts.

02

Chained to a laptop.

Close the lid and the work stops, or you stop seeing it. There is no checking in from your phone on the way home.

03

Context lives somewhere else.

The issue is in Linear, the thread is in Slack, the review is in GitHub. You copy it all into a prompt by hand.

One session. The whole team in it.

Every task streams live to everyone with access to the repository. Watch the agent work, add context while it runs, and see exactly who said what.

Illustration of a Rivets task. Marc Fowler asks the agent to rotate refresh tokens. While it runs, James Murphy steers it to keep the old route working. A queued message from Marc waits with Edit and Send now controls, and the Changes panel lists four edited files.

Presence

See who is in the task and who is typing. Every member with access gets the same live stream.

Anyone can steer

Any member can message the running agent. Every message carries the name of the person who sent it.

Interrupt or queue

Deliver a message now, or queue it. Queued messages can be edited, deleted or sent early before the agent takes them.

Live Changes

The Changes view follows the agent as it edits, refreshed after every write. Everyone reviews the same diff.

Start from the tool you have open.

Issues, threads and pull requests already hold the context. Rivets picks up work where it lives and reports back there too.

Delegate a Linear issue.

Delegate or @mention Rivets on an issue and work starts. Progress, Agent Plans and follow-ups stay in sync, and the pull request links back with “Fixes ABC-123”.

Ask in Slack.

Mention Rivets in a channel or DM the app. The assistant starts tasks, checks on them and answers in the thread. Each thread is one conversation.

Pick up a pull request.

Start a task from any pull request or branch. The Checks tab takes it the rest of the way, from push to merge.

Native on Mac, iPhone and iPad.

The Mac app has a project tree, a ⌘K palette and a worker built in. On iPhone and iPad, follow every task, steer the agent, and get a push when a job finishes.

  • macOS 15 and later
  • One universal app for iOS and iPadOS 18
  • Push notifications when a job finishes
The Rivets iPhone app's Tasks tab, listing tasks grouped by repository with branch names, chat counts and line changes.

Any MCP client.

Add app.rivets.dev/api/mcp with a personal token. 29 tools cover tasks, git and Linear.

Or just a browser.

Nothing to install. Start tasks, steer agents, review diffs and merge from any computer, at app.rivets.dev.

Your machines. Your subscriptions.

A worker is any machine running the Rivets CLI, or the Mac app. It runs Claude Code or Codex in a git worktree per task and streams the session back. Rivets never bills for inference.

Connect a machine in one command.

Create a worker in Settings, paste the one-time token, and it is ready for tasks.

$ rivets worker connect --token-stdin

Add rivets worker install to keep it running as a per-user background service. It updates itself when idle.

Runs on

  • macOS
  • Linux
  • Windows
  • arm64 and x64

Install the Mac app and your Mac is a worker out of the box.

Claude Code and Codex, on the plans you already pay for.

Pick the agent and model per run. Your defaults follow you across web, Mac and iPhone.

Claude Code

  • Opus 5.5
  • Fable 5.1
  • Sonnet 5.5
  • Haiku 4.5

Codex

  • GPT-6 Astra
  • Sol
  • Luna

Per run

  • Effort, low to ultra
  • Fast mode
  • Plan mode

Your subscriptions

Every model call runs through your own CLI. Each worker reports its session and weekly usage.

Credentials stay put

The GitHub App issues short-lived tokens. The worker never reads your personal tokens or SSH keys.

Signed requests

Worker tokens live in the OS keychain, and every request is signed with a key held on the machine.

One button walks the branch to merge.

The Checks tab always shows the next step. Press it and Rivets does the git work, or hands the problem back to the agent.

  1. Create PR

    Title and description written for you

  2. Push changes

    Commit and push in one step

  3. Checks

    Runs, deployments and reviews

  4. 4

    Resolve

    Conflicts and review threads

  5. 5

    Mark ready

    Draft to ready for review

  6. 6

    Merge

    Squash, merge commit or rebase

Written with AI, on your worker

PR titles, descriptions and commit messages come from your own agent. Text you wrote yourself is never replaced.

Conflicts handed to the agent

Rivets merges the base branch locally and asks the agent to resolve what conflicts. You choose to continue or abort.

Fix review threads

Unresolved threads show up in Checks. Fix sends the thread straight to the agent working on the branch.

Archived on merge

When the pull request merges, the task archives itself. That includes merges done on GitHub.

Everything a team needs around the agent.

Automations

Run a saved prompt hourly, daily or weekly across repos. Each run is a normal task, and your app does not need to be open.

Run scripts

Define setup and run commands in .rivets/settings.toml. Every client gets a Run control, and output is visible to the team.

Terminals

Open terminal tabs on the worker, or launch Claude Code or Codex interactively in one. Scrollback survives reconnects.

Custom prompts

Tune the instructions behind task naming, commit messages, pull requests and code review, per organization, account or repository.

Handoffs

Hand a conversation to another agent with its recent transcript, or move it to another worker along with its files.

Teams and permissions

Group members into teams and grant each team the repositories it needs. Invite by email or link.

Security

Two-factor sign-in with backup codes, signed worker requests, and native devices you can revoke from Settings.

An assistant, not another agent

Press ⌘J to ask what is running or to start a task. It delegates to your agents and runs on the cheapest model.

Questions, answered.

What is Rivets?

Rivets is a multiplayer coding-agent orchestrator. You connect your own machines as workers, send tasks to the Claude Code and Codex CLIs running on them, and watch and steer the sessions with your team in real time.

Which agents and models does it support?

Claude Code and Codex. Claude models include Opus 5.5 (the default), Fable 5.1, Sonnet 5.5 and Haiku 4.5, plus earlier versions. Codex models are read from your installed CLI, including GPT-6 Astra, Sol and Luna. You choose the model, reasoning effort, fast mode and plan mode for each run.

Do you proxy or resell model tokens?

No. Every model call runs on a worker through your own Claude Code or Codex CLI, on your own subscription. Rivets has no AI of its own and never bills for inference.

Does my code go to Rivets?

Agents run on your machines, in a git worktree per task. The Rivets backend relays the session to your team and stores snapshots of git status and diffs after each edit, which power the live Changes view. Repositories are cloned onto your workers using short-lived tokens from the Rivets GitHub App.

Can teammates step in while an agent is running?

Yes. Anyone with access to the repository can watch the stream and steer the agent. Each message is attributed to its sender. You can interrupt the agent right away or queue a message, and queued messages can be edited or sent early.

Which platforms does it run on?

Workers run on macOS, Linux and Windows, on arm64 and x64. The apps run on the web, macOS 15 and later, and iOS and iPadOS 18 and later. The iPhone and iPad app follows and steers work but never runs a worker.

Is Rivets open source?

No. I build Rivets at Frontier.sh, and your agents run on your own machines with your own Claude Code or Codex subscription.

How much does Rivets cost?

Rivets is free while it’s in beta. At launch I’ll offer special launch pricing for early teams, then lifetime licenses after that. Model usage always runs on your own Claude and Codex subscriptions, so Rivets never bills for inference.

When can I get access?

Early access is rolling out now. Join the list and I’ll get in touch as soon as I can.

Bring your team into the session.

Rivets is rolling out in early access. Leave your email and I’ll get in touch as soon as I can.