dots coding-agents and dots git

The dots coding-agents and dots git families, command by command. Every signature, argument, and option below is read from the CLI's own command tree, so this page cannot drift from dots --help. Every other family is listed in CLI Reference.

dots coding-agents

dots coding-agents [options] [command]

Sync this machine's local coding-agent conversations (Claude Code, Codex, Cursor) into your Dotabases.

dots coding-agents sync

dots coding-agents sync [options]

Back-fill this machine's consented coding-agent sessions to your API once, then exit — printing the imported / skipped / failed summary. The canonical one-shot.

Options:

• --source <sourceKey> — Limit to one detected source key (<platform>:<folder-hash>); repeatable. Default targets every detected source.
• --consent — Record consent for the targeted sources before anything is read (bare: every detected source). A source with no recorded consent is never read.

dots coding-agents watch

dots coding-agents watch [options]

Catch up, then tail this machine's consented coding-agent sessions in real time, pushing each change to your API. Runs in the foreground until interrupted (Ctrl-C). Diagnostics go to stderr; stdout stays empty. For a one-shot backfill, use coding-agents sync.

Options:

• --source <sourceKey> — Limit to one detected source key (<platform>:<folder-hash>); repeatable. Default targets every detected source.
• --consent — Record consent for the targeted sources before anything is read (bare: every detected source). A source with no recorded consent is never read.

dots coding-agents detect

dots coding-agents detect [options]

Read what the SERVER detects on its own filesystem, folded together with the recorded consent decisions — each folder's key, agent kind, profile path, session count, and whether it is consented. A DEPLOYED API cannot see this machine, so it reports nothing there; a local daemon reports the same folders sync finds. To act on what THIS machine holds, use coding-agents consent set, which attests from the local detect run.

dots coding-agents consent

dots coding-agents consent [options] [command]

Read and record the per-folder consent decisions that gate every transcript read.

dots coding-agents consent set

dots coding-agents consent set [options]

Record consent for coding-agent source folders and enqueue the server-side backfill for the ones this server can read, printing the initial backfill status. Consenting a set also marks every OTHER folder the server currently detects as dismissed — this run's decision wins.

Options:

• --source <sourceKey> — A source key (<platform>:<folder-hash>) THIS machine detects; repeatable. Sent as an ATTESTED folder — the key plus the kind this machine's own detect run produced — because a deployed API cannot see this filesystem. A key this machine does not detect is a usage error before any request. Default attests every detected source.
• --server-key <folderKey> — A folder key only the SERVER detects (the local-daemon posture); repeatable. Sent bare for the server's own detection to confirm — a key the server cannot detect records nothing. Use coding-agents detect to read what it sees.

dots coding-agents consent read

dots coding-agents consent read [options]

Read the recorded per-folder consent decisions for this workspace, ordered by folder key. Only DECIDED folders appear — an absent folder means no decision was ever recorded, which is never consent. The route answers the whole set, so --limit/--offset window what it returned.

Options:

• --limit <n> — Maximum records to return.
• --offset <n> — Records to skip before returning the page.
• --count — Print the number of records this list returns instead of the records themselves.

dots coding-agents consent-evidence

dots coding-agents consent-evidence [options]

Read the consent/read ordering evidence for consented sources: when each consent was decided and when its backfill reader first ran. A missing read timestamp stays absent rather than being manufactured, so an ordering rehearsal fails closed on it instead of claiming completion.

dots coding-agents dismiss

dots coding-agents dismiss [options]

Mark coding-agent folders prompted-not-consented — the "Not now" memory that re-surfaces gently rather than auto-opening. This WITHDRAWS consent for a folder that had it: the decision row flips to dismissed and its recorded decision time is overwritten, so nothing reads that folder again until consent is recorded afresh. Only folders the SERVER detects are affected. Returns the refreshed detection result.

Options:

• --yes — Confirm the destructive action (required; it cannot be undone).
• --dry-run — Resolve and report what would change; writes nothing.
• --source <folderKey> — A folder key the SERVER detects (read them with coding-agents detect); repeatable. Omit to dismiss every folder the server currently detects.

dots coding-agents backfill

dots coding-agents backfill [options] [command]

The server-side backfill of consented coding-agent sources.

dots coding-agents backfill status

dots coding-agents backfill status [options]

Read the per-source backfill status — each source's state and imported / total / skipped / failed counts, the rolled-up aggregate, and the live dead-letter count for sessions still awaiting a retry.

dots coding-agents backfill retry

dots coding-agents backfill retry [options]

Re-drain the coding-agent dead-letter queue: re-enqueue the sessions whose backfill failed, and print the refreshed status. A job runner that cannot be reached is reported server-side rather than failing the call, so the status still returns.

dots git

dots git [options] [command]

Ingest git history — local commits (no credential) and PAT-fetched GitHub pull requests.

dots git ingest-commits

dots git ingest-commits [options] <path>

Ingest a local repository checkout's git commit history into the Git Commits Dotabase — one row per commit, keyed on the full 40-char SHA. Parses git log locally (no credential needed) and uploads the mapped records in batches; Category and scope tags are derived from each Conventional-Commit subject server-side. repo ingest already ledgers the commits its shipment carried metadata for, so this fills what the carry left behind — a history past the carry bound, or a checkout its reader could not open. A re-ingest with no new commits is a no-op (idempotent on the SHA).

Arguments:

• <path> — Path to the local repository checkout whose commit history to ingest (resolved to an absolute path).

Options:

• --cold-start — Force a full-history read: skip the already-ingested watermark lookup entirely and parse every commit in the checkout. Use it after a history rewrite, or to re-state the whole history.

dots git fetch-prs

dots git fetch-prs [options] <target>

Fetch a GitHub repository's pull requests into the Pull Requests Dotabase using a GitHub PAT (set GH_TOKEN or GITHUB_TOKEN). Pages through every PR (open/merged/closed), records each PR's member-commit SHAs for the edge pass, and uploads the mapped records in batches. A resumable cursor means a rate-limit or interrupt resumes rather than restarts; a re-fetch is idempotent on the PR node id. With no token set it refuses with a message and writes nothing.

Arguments:

• <target> — The GitHub repo to fetch PRs for: an owner/repo slug, or a local checkout path whose GitHub origin remote resolves it.

dots git watermark

dots git watermark [options] <repository>

Read one repository's newest already-ingested commit SHAs (newest first, server-capped) plus its total ingested count — the delta read git ingest-commits makes for itself before it parses any history. An unprovisioned Git Commits Dotabase is a typed 404; a repository with nothing ingested answers an empty SHA list and a count of zero.

Arguments:

• <repository> — The stored repository IDENTITY, exactly as the ingest stamps it: owner/repo for a checkout with a GitHub origin remote, else that checkout's directory name. A path is NOT resolved here — pass the identity git ingest-commits reported.

dots git coverage

dots git coverage [options] <sha...>

Read exact Git Commit ledger coverage for a bounded set of commit SHAs: how many were requested, how many are ledgered as active rows, and how many are missing. SHAs are validated and de-duplicated before anything is sent, and an over-cap set is chunked across requests.

Arguments:

• <sha> — One or more full 40-char lowercase commit SHAs; repeats are counted once. A malformed SHA is a usage error before any request.

generator: apps/docs/pipeline/generate-reference.ts — regenerate with pnpm --filter @dots/docs docs:generate:reference; a hand edit to this page fails the docs drift gate.