Reference

Opens browser login, receives a local callback, and stores the generated API token securely in your system keychain or an encrypted config file.

Copyrepost auth login

If a token is already saved, this command keeps the existing token and will not replace it. Run repost auth logout first when you need to switch accounts.

Stores an API token for non-browser authentication. If TOKEN is omitted, the CLI reads from stdin. Tokens must start with rp_ and be exactly 43 characters long.

Copyrepost auth token rp_your_token_here

Validates the current token against the Repost API and prints a summary. When server validation succeeds, the output includes:

• Token name
• Token type (personal or organization)
• Token prefix
• Scopes
• Creation time
• Last-used time
• Expiration date
• Auth method (stored token or REPOST_TOKEN environment variable)

Copyrepost auth status

If a stored token has been revoked server-side, the CLI removes the local copy and asks you to authenticate again.

Attempts to revoke the stored token on the Repost server, then removes the token saved in local secure storage.

Copyrepost auth logout

Scaffold a new schema workspace: creates repost/schema.repost (a generator block plus a small working example), a .env placeholder, and a .gitignore that covers .env and the generated output. Refuses if repost/ already exists. Interactive on a terminal; pass the flags to run headless.

Copyrepost schema init --language java --output ./src/main/java

Parse and validate .repost files without writing output. The exit code reflects the diagnostics, so it is CI-friendly.

Copyrepost schema validate

Validate, then emit each generator's SDK (typescript, go, python, java, or kotlin) and the JSON Schema into the path its generator block points at. No migration is written. It refuses (hard error) when the migration lineage has a fork or a hand-edited snapshot, and warns on stderr, but still generates, when the schema has unmigrated changes.

A Java or Kotlin generator also needs packageName, clientName, and a resourceOutput root (for the client.json registry) alongside output. JVM projects usually generate through the Maven (repost:generate / repost:check) or Gradle (repostGenerate / repostGenerateCheck) plugin rather than the CLI. See the Java and Kotlin guides.

Copyrepost schema generate

Diff the current output against the previous state; when it changed, write a new repost/migrations/<timestamp>_<name>/ snapshot (the directory is prefixed with a UTC YYYYMMDDHHMMSS timestamp), bump the affected event versions, and regenerate. No change is a no-op. Each migration records its parent (or parents for a reconciliation) and a checksum of its snapshot.

--name is optional: when a migration is written and it is omitted, the command prompts for a name on a terminal (an empty answer gives a timestamp-only directory) and errors when stdin is not a terminal.

When the migration would remove event types, it lists them and requires an explicit y on a terminal (default No), or --accept-removals to proceed non-interactively. This is the one command that reconciles a fork: it diffs the merged schema against every head, prints a per-parent summary, and records parents: [...].

Copyrepost schema migrate dev --name add_subtitle

After merging a branch that added migrations, run repost schema migrate dev once to write a reconciling migration; in CI, use repost schema migrate status (below) as the gate.

Report migration health without writing anything. This is the CI gate. Exit code 0 with a one-line summary when the lineage is clean; non-zero with a line-per-finding report when a merge left a fork, when the schema has unmigrated changes (the emission differs from the last snapshot, so migrate dev is not a no-op), or when a snapshot's checksum no longer matches (a hand-edited or corrupted artifact).

Copyrepost schema migrate status

Apply the committed migrations to a live Repost environment: sends the migration head, the full lineage, and the accumulated schemas.json; the server materializes the event-type registry. Requires a clean local status: a fork, unmigrated changes, or a checksum mismatch is a hard error. Re-deploying the same head is a no-op. A server head that is not in your lineage refuses the deploy with a machine-readable reason: behind (your checkout is stale; git pull the latest migrations and redeploy) or diverged (the histories have split; reconcile by git-merging the deployed migrations and running migrate dev, or replace the deployed history with --force).

Auth: REPOST_TOKEN (an environment-scoped token with the schema:deploy scope) and optionally REPOST_API_URL, read from repost/.env before the process environment.

--force replaces a diverged (or rolled-back) deployed history: the CLI fetches the deployed head, shows what will be replaced, and asks for confirmation, then echoes that head back as an optimistic lease. If the head moves between the look and the deploy, the force is refused. Forcing to an older, previously deployed checksum rewinds the registry (the rollback path).

Copyrepost schema migrate deploy

Push the current schema to a live Repost environment without a migration artifact: Prisma's db push, for dev and staging loops. Refused on environments that already have migration history, so a push can never fork a production lineage. The payload is checksummed from the emission itself, so repeat pushes of an unchanged schema are no-ops. Same auth as migrate deploy.

Copyrepost schema push

Convert a Svix environment export into a repost/ workspace.

Copyrepost schema import svix export.json --out app

Format .repost files in place. Idempotent.

Copyrepost schema fmt

Prints the authenticated identity, active organization, plan, and usage. Schema repost.whoami/v1. No command-specific flags.

Prints the machine-readable command manifest: paths, usage, descriptions, command kind, group IDs, output mode, agent contract status, output schema names, and flags. Always JSON. Cache it by its version field.

Prints one command's output schema, output mode, runtime envelope shape, and a data_shape when one is documented. Schema repost.command_schema/v1.

docs search prints the query cheatsheet. docs agent prints the operating manual. Output is Markdown.

Search received events. Schema repost.events.search/v1. Returns next_cursor/has_more for forward paging.

Fetch one event with credentials redacted by default. Schema repost.events.get/v1. Body truncates to 4096 bytes unless --full.

Compare two events after default redaction. Schema repost.events.diff/v1.

Infer a JSON schema from event bodies or supplied samples. Schema repost.events.schema/v1.

Search delivery attempts. Schema repost.forwards.search/v1.

The authoritative per-attempt delivery timeline for one event and forwarder. Schema repost.forwards.chain/v1.

List dead-letter rows for a bucket or forwarder. Schema repost.dlq.list/v1.

Forwarder health over a window, with optional threshold gating. Schema repost.health/v1.

Block until one matching event arrives on the observe stream. Emits a bare JSON object (no envelope) and exits 0; exits 7 on timeout.

Stream compact, redacted events as NDJSON (one object per line). Set at least one bound.

Create a bucket and an external forwarder in one step. Schema repost.init/v1.

Promote a temporary guest webhook setup into account-backed resources through the browser-confirmed local callback flow. Schema repost.promote.setup/v1. The command first emits status: "requires_user_action", then either status: "completed" after the CLI receives the browser callback or status: "failed" before exiting non-zero.

create provisions a bucket (schema repost.bucket.create/v1); get returns a bucket plus its forwarders (schema repost.bucket.get/v1).

Create a forwarder on a bucket. Schema repost.forwarder.create/v1. --target is required for EXTERNAL forwarders.

Preview or create a forwarder-scoped replay. Schema repost.replay.create/v1. A single explicit event ID needs no --yes; a --query or --dlq selection, or multiple IDs, require --yes unless --dry-run.

Inspect and steer replay jobs by ID. status/wait → repost.replay.status/v1; list → repost.replay.list/v1; replay pause / replay resume / replay cancel → repost.replay.action/v1.