Command reference
Every command accepts the global flags
(--url, --instance, --secret, --json). Arguments shown in <angle brackets> are positional; --flags are optional unless noted.
Instance linking
Section titled “Instance linking”| Command | Arguments | Description |
|---|---|---|
login <url> | --secret | Link an instance and store its secret (validated against /health). Prompts for the secret if not passed; --secret is required when non-interactive. |
logout [host] | Remove a linked instance and its stored secret. Defaults to the current instance. | |
use <host> | Switch the current instance. | |
instances | List linked instances and mark the current one. |
status
Section titled “status”notewright statusAggregate instance health: the running core version, the composed notes and
followUp provider ids, and a row per Durable Object showing whether it is
healthy. Calls GET /status.
notewright startWake every Durable Object so its onStart() runs and (re)registers its cron
schedule. Prints the schedules each DO registered. Run this after a fresh deploy.
Calls POST /start.
notewright syncTrigger a notes sync now. Calls POST /sync, which forwards to the notes source’s
sync DO when the source declares a sync binding, or runs inline otherwise.
schedules
Section titled “schedules”notewright schedulesShow the registered cron schedules per Durable Object, with the next run time.
Reads GET /status and renders the schedule rows.
follow-ups
Section titled “follow-ups”Follow-up extraction operations.
| Command | Arguments | Description | Endpoint |
|---|---|---|---|
follow-ups run <meetingId> | --force | Enqueue follow-up extraction for one meeting. --force clears the failure and run marker first (keeps task mappings). | POST /follow-ups/run |
follow-ups backfill | --since <iso>, --force | Enqueue extraction for a date range. --since is an ISO8601 lower bound (defaults to the server default). | POST /follow-ups/backfill |
follow-ups health | Follow-up agent health and unresolved failure count. | GET /follow-ups/health | |
follow-ups runs | --since <iso>, --limit <n> | List processed meeting runs (default 50 rows). | GET /follow-ups/runs |
follow-ups mappings <meetingId> | List the task mappings created for a meeting. | GET /follow-ups/mappings |
notewright follow-ups run mtg_123 --forcenotewright follow-ups backfill --since 2026-05-01T00:00:00Znotewright follow-ups runs --limit 20failures
Section titled “failures”Inspect and clear follow-up failures.
| Command | Arguments | Description | Endpoint |
|---|---|---|---|
failures list | --limit <n> | List unresolved failures with the error detail (default 50 rows). | GET /follow-ups/failures |
failures clear | --meeting <id>, --all, --yes | Clear failure rows. Pass --meeting <id> for one, or --all for every row. --all prompts to confirm; pass --yes to skip the prompt (required when non-interactive). | POST /follow-ups/failures/clear |
notewright failures listnotewright failures clear --meeting mtg_123notewright failures clear --all --yesTo clear a failure and immediately retry, use follow-ups run <id> --force.
meetings
Section titled “meetings”Read synced meetings.
| Command | Arguments | Description | Endpoint |
|---|---|---|---|
meetings list | --since <iso>, --limit <n> | List synced meetings. | GET /meetings |
meetings get <id> | --transcript | Fetch one meeting; --transcript includes its transcript. | GET /meetings/get |
notewright meetings list --limit 25notewright meetings get mtg_123 --transcriptspeakers
Section titled “speakers”Speaker-context operations.
| Command | Arguments | Description | Endpoint |
|---|---|---|---|
speakers resolve <meetingId> | --version <v> | Resolve speaker context for a meeting. --version is the transcript version (looked up if omitted). | POST /speaker-context/run |
speakers get <meetingId> | --version <v> (required) | Fetch a cached speaker resolution for a transcript version. | GET /speaker-context/get |
speakers health | Speaker-context agent health. | GET /speaker-context/health |
notewright speakers resolve mtg_123notewright speakers get mtg_123 --version 2026-06-01T12:00:00Zdoctor
Section titled “doctor”notewright doctornotewright doctor --check-remoteReport-only local infra preflight. No network unless --check-remote, which
queries the remote D1 migrations table via Wrangler. See
doctor preflight for what it checks. This command runs
locally against your composed project, not against a linked instance, so it does
not use the global connection flags.