co-maintainer

Cloud

The hosted service at cloud.co-maintainer.com runs serve for you, so your team gets shared repository context without operating a server. This page explains how it relates to the CLI and the self-hosted setup.

Self-hosting stays supported. Cloud is the same binary with the same database and the same remote review API, only managed for you.

What cloud gives you

Piece Detail
Managed serve The dashboard, the job worker, and the webhook receiver
Per-team instances Each team gets its own instance and host name
Repository context init and sync run on the instance, not on every laptop
Remote review Developers keep using review --remote against the instance
GitHub App Created from the dashboard, the same flow as self-hosted

Connecting the CLI

The connection is identical to a self-hosted server: a host and a cmr_ token.

  1. Sign in to your instance and open Settings, Remote review.
  2. Create a token and copy it once.
  3. On the laptop:
co-maintainer set --remote-host=https://<your-instance> --remote-token=cmr_...
cd your/clone
co-maintainer review --remote

The CLI needs no local init for that repository, because the guides live on the instance. See Remote review for the full flag list and the codegraph behavior, and Authentication for how the token fits with the other credentials.

You can read the exact guides your review will use before running it:

co-maintainer view owner/repo --remote

Putting a repository on the instance

Open the dashboard, choose Add repository, and confirm the plan. This is the same flow as self-hosted, including the read-only probe and the cost estimate. The dashboard needs the GitHub App installed on the repository, which the Create GitHub App button sets up for you.

Mixing cloud with local CLI

A team can keep using the CLI for local and PR review while cloud holds the shared context. The two do not conflict:

If you want Run it
Feedback on your working tree, before a push review with local guides
Feedback using the team's shared context review --remote against the instance
A PR reviewed automatically The GitHub App on the instance
A repository onboarded once for everyone Dashboard Add repository

Support and status

The instance list, uptime, and any incident notes are published by the co-maintainer maintainers. For a self-hosted deployment, the same pages under Serve and the Dashboard apply.

If a remote review fails, Troubleshooting lists the token and connectivity messages, and Data and privacy says what the instance stores.