CLI reference

The repome CLI is the canonical shell client for the API. Every command also accepts --json for machine-readable output; JSON is the default when stdout is not a TTY.

Global flags

Recognised anywhere in argv (before or after the subcommand):

Repo names are bare — the server resolves them against your active org. There is no per-command org override; switch the active org with repome org switch <slug>.

repome init

Authenticate the CLI, set up your active org, and optionally link the current directory to a repome repo. An organization is auto-created at signup. Idempotent — re-running surfaces current state without destructive changes.

repome init
repome init --no-link

Behavior:

• no auth → device-flow login
• active org set → report it
• no active org yet → activate the account's oldest org
• inside a git repo → offer to write .repome/config.json (--no-link skips)

repome whoami

Print the active authentication, organization, and resolved repo context. Exits 0 even when unauthenticated so agents can use it as a probe.

repome whoami

repome auth

Bare repome auth is a back-compat alias for repome auth login.

# Print the active key for scripting
export REPOME_API_KEY=$(repome auth token)

# Or use it directly with curl against the oRPC endpoint
curl -X POST -H "$(repome auth token --header)" \
  https://api.repome.sh/api/rpc/health/ping

repome org

An organization is auto-created when you sign up — its name is derived from your display name or email (renamable later). Org slugs are opaque, server-minted handles (org-…): copy them from repome org list, don't invent them.

repome repos

repome repos list
repome repos create hello-world --description "..." --default-branch main
repome repos import site --from https://github.com/acme/site.git
repome repos delete hello-world --yes

For ephemeral, no-auth repos, see repome anon.

repome anon

Manage anonymous, ephemeral repos that don't require authentication. Identity is a local anonId stored in ~/.config/repome/anon.json (or set via REPOME_ANON_ID). Anon repos are owned by that anonId and expire after the TTL chosen at creation time.

repome anon create --ttl 6h
repome anon list
repome anon clone <name> /tmp/scratch
repome anon share <name> --role write --expires 2h
repome anon delete <name> --yes

repome anon share mirrors repome share for anonymous repos: it mints an owner-scoped share token and prints a clone URL that works with bare git — no account, no repome CLI on the recipient side. A share can never outlive the repo (the TTL is clamped to the repo's remaining lifetime), and repome anon delete <name> is the kill switch for every share. --link creates a secure invite instead (see repome invites), clamped to the repo's expiry; manage those with repome anon invites list / repome anon invites revoke <id> (anon invites belong to your local anonId, not a logged-in session).

repome git

Read and clone git content via the API — no shell-out needed for log, show, ls, branch, tag, compare, or diff.

repome git clone hello-world
repome git log hello-world --oneline -n 20
repome git ls hello-world src/ -r

repome git clone and repome anon clone read the repo's API-returned storage remote, mint a short-lived token, and install local credentials for the clone.

repome link / repome unlink

Write or remove .repome/config.json in the current directory so subsequent commands resolve the repo automatically.

# Auto-detect from `origin` when inside a clone, or pass an explicit name
repome link
repome link --repo hello-world
repome unlink

The link file records the bare repo name. That name resolves against your active org, so switching orgs re-points the link; if the repo does not exist in the new active org, repo and git commands surface REPO_NOT_FOUND.

repome tokens

repome tokens mint hello-world --scope write --op agent
repome tokens list hello-world
repome tokens revoke hello-world <id>

You can always revoke tokens you minted yourself (so the revoke command printed by repome share works for every sharer); revoking anyone else's tokens requires repo admin.

--op selects the TTL cap and must be one of refs, object, merge, seed, clone, agent, or share. Use agent for general write tokens; share is the long-lived tier behind repome share. Git credential-helper requests derive push/fetch scope through the API's tokens.mintForGitRemote path.

Repo tokens are for git remote operations. Use API keys from repome keys when calling the RPC API or SDK.

repome share

One command to onboard a single human or agent to one specific repo — without org membership, accounts, or short-lived git-wire tokens. A share is a long-lived, repo-scoped, revocable token embedded in a clone URL: whoever holds the link has the granted access (bearer semantics).

repome share my-api --role write --expires 7d

Every share prints:

• a clone URL that works with bare git clone (the credential is percent-encoded into the URL — treat the whole URL as a secret),
• the .repome/config.json link snippet for the recipient's clone,
• a paste-ready onboarding block that reads the same for a human or an agent (--out FILE writes it to a file), and
• the exact repome tokens revoke … command that kills the share.

Inside a linked directory repome share needs no name; manage shares with repome tokens list / repome tokens revoke.

Secure invite links (--link)

repome share --link prints an unguessable https://repome.sh/invites/<id> capability URL instead of a credential-bearing clone URL — safe to paste in chat, because the invite id is the only secret in the link:

repome share my-api --role read --link

Opening the invite renders the onboarding instructions; a fresh, short-lived git credential is minted only on an explicit Reveal action (never on a bare GET, so link previews can't consume it). Agents can fetch the same invite as raw markdown at /invites/<id>.md?reveal=1. Invites are revocable (repome invites revoke <id>), expiring, and policy-bounded (maxReveals); repome stores only a hash of the invite id and never stores a live credential.

repome invites

Manage the secure invite links created by repome share --link.

repome invites list
repome invites revoke <id>

Invites created by repome anon share --link belong to your local anonId rather than a logged-in session — manage those with repome anon invites list / repome anon invites revoke <id>.

Revoking an invite stops future reveals immediately; credentials already revealed stay valid until their short TTL expires (revoke those with repome tokens revoke). Treat every invite URL like a password.

repome keys

Create, list, and delete additional API keys for CI, API, and SDK consumers. Scopes are repeatable.

repome keys create ci --scope repos:read --scope tokens:mint
repome keys list
repome keys delete <id> --yes

Available scopes: repos:read, repos:write, tokens:read, tokens:mint, tokens:revoke, orgs:read, orgs:write, members:read, members:write, keys:read, keys:write, agents:invoke.

repome members

Members commands administer the active org. Switch the administered org with repome org switch <slug>.

repome doctor

Check the CLI's local configuration: auth store, file permissions, server reachability, and the git credential helper.

repome doctor

repome git config-credential-helper

Install or remove the git credential helper for repome remotes. repome git clone wires credentials for the clone automatically; this command is useful when you manage remotes yourself.

repome git config-credential-helper --global
repome git config-credential-helper --global --uninstall

Agent discovery endpoints

The docs site exposes canonical bytes for coding agents alongside the rendered pages:

See /docs/agents for the install-the-skill walkthrough.