Every ki command
All 88 commands, in the 14 groups the CLI itself divides them into. The groups are ordered by scope: what affects your machine, then what affects one repository, then what affects the estate.
This inventory is vendored, not rewritten. ki ships a manual page, and this page takes it verbatim from v0.4.0 — every invocation and every description below is the tool's own text, parsed rather than paraphrased. A command renamed, added, or withdrawn upstream cannot leave this site describing one that is not there. The parse reads both of the manual's inventories and reconciles them, because at this release they disagree: one group appears in the synopsis and not in the reference section. It is published below, marked.
What the site adds is the routing around it. If you do not know which command you want, the CLI overview explains what each group is for and which concept page covers it. If you know the outcome but not the mechanism, choose a skill by outcome may be the better starting point, because much of what ki does is activate a capability rather than perform the work itself.
Reading an entry
An invocation is written the way the manual writes it. <angle-brackets> mark a value you supply, [square brackets] mark an optional part, | separates alternatives, and ... marks a repeatable option. [repo-options] stands for the repository selectors in the Repository options group, which any ki repo command accepts.
The version you have installed is the authority on exact grammar. ki --help and ki <command> --help answer from your binary; this page answers from v0.4.0, which is the release this site currently advertises.
General
Use these commands to invoke KI; use --help for command-specific guidance.
ki [command]
Run a KI command, or print root help when no command is supplied.
Global options
Use these options with ki or any KI command to print command help or the CLI version.
--help, -h
Print help for KI or the selected command.
--version, -V
Print the CLI version.
Installation
Use this command to bootstrap the user-managed KI environment.
ki bootstrap
Create the user-managed KI environment configuration from detected supported agents, install the built-in verified canonical harness, then install the core user skills — ki-bootstrap, ki-next, ki-plan, and ki-recap — into every configured agent's user skill directory. An existing agent configuration is reused without replacement. Pass --refresh to redetect every supported runtime and rebuild the user configuration's agents, installed harnesses, and KI-managed user skill links. During a refresh only, KI imports the retired [repositories].paths list into keyed records in $XDG_STATE_HOME/ki/registry.toml and removes that list from user configuration. Normal repository, trade, and Agora resolution never reads the retired path list.
Local management
Use these commands to inspect the local KI installation, user configuration, and repository state without changing it.
ki manage search <query>
Search only verified installed local harness capabilities. The required non-empty query matches case-insensitively against a harness identifier, capability kind, or capability name. Results are sorted by harness identifier, capability kind, and capability name. The command neither discovers a repository nor consults a registry or the network. When no capability matches, it succeeds and reports that no matching installed capabilities exist.
ki manage completion <shell>
Print Bash or Zsh completion source to standard output. The generated scripts follow the complete registered command tree, offer valid option names at every reachable command, complete documented closed values, and delegate repository selection, capture-directory, and output-directory values to the shell's native path completion. They do not invoke KI, consult the network, or invent dynamic identifiers.
ki manage outdated
Report installed harnesses only when comparable newer release evidence is available; it names unavailable evidence rather than claiming freshness.
ki manage missing
Report desired user capabilities that have no installed provider.
ki manage update [--cli]
Refresh installed configured harnesses. The executable updates only when a verified installer receipt proves that it owns the running regular executable. Use --cli to require that executable target. Linked development and externally managed executables, including Homebrew installations, are not self-updated.
ki manage cleanup
Report only stale artefacts in a persisted, versioned KI-owned format. V1 has no such format, so this command reports that no eligible managed stale state exists and changes no files. It does not infer that cache contents, transaction-looking directories, unconfigured harnesses, links, or unknown files are stale.
ki manage diag
Print the CLI version, installation mode, resolved paths, and user configuration, registry, and managed local-development state without changing state. It does not inspect repository declarations or projections.
ki manage doctor
Check the user configuration, configured agent skill directories, installed harnesses, and configured KI user-skill links without changing state. It also reports direct-CWD legacy .ki-meta/ and .ki/ directories, without searching for or operating on a repository. It validates a regular direct-CWD .ki.toml declaration without resolving its providers. A failing check produces a non-zero exit status after the complete report.
ki manage repair [--dry-run]
Reconcile configured user-skill links from their installed or active local harness sources. It creates missing links and re-points stale or dangling symbolic links, but never changes configuration, installs a harness, removes legacy repository state, or repairs repository projections. It reports unavailable sources, incompatible agents, and unsafe non-symbolic-link entries for manual resolution. With --dry-run, it reports proposed links without changing state.
ki manage docs [topic]
Print canonical documentation locations without opening a browser, fetching content, or discovering a repository. With no topic, it prints every available location with an explanatory prefix. The supported topics are overview for https://knowledgeislands.info/tooling/ki/, site for https://knowledgeislands.info/, manual for https://github.com/knowledgeislands/tools-ki/blob/main/man/ki.1 and roadmap for https://github.com/knowledgeislands/tools-ki/blob/main/ROADMAP.md. Any other topic is invalid command grammar.
ki manage list
List verified installed harnesses and their capabilities with declared user skills and local registered repositories. The command does not fetch, discover a repository, or change state.
ki manage vscode check
Compare chezmoi-managed VS Code workspaces and trusted-folder source state with the local KI repository registry. Report a source diff and exit non-zero when drift exists. This command never writes.
ki manage vscode sync [--write]
Preview the same reconciliation. With --write, publish the reviewed changes to chezmoi source state. This command never runs chezmoi apply.
ki manage vscode source create <repository> [--write]
Preview creation and workspace association of an opt-in OneDrive source store for one registered repository basename or absolute path. With --write, create the directory and publish corresponding chezmoi source-state changes. Ambiguous repository or legacy source-store matches fail closed.
User management
Use these commands to inspect installed capabilities and manage the skills declared in the user-managed KI environment.
ki skill add <skill> [--replace]
Add a registered skill in configured user agent skill spaces.
ki skill remove <skill>
Remove a KI-managed user skill link.
Repository options
Use this shared option with any ki repo command to select one or more repositories. It appears after ki repo and before the command.
--repo <path-or-pattern>
Repeat this option to select literal repository roots or patterns in supplied order. KI resolves every target physically before an operation begins and rejects unmatched patterns, invalid roots, and duplicate physical roots.
--agora <name>
Select every member of one declared named Agora, or every registered canonical repository through the reserved estate selector. This option, --repo, and --estate are mutually exclusive. Each member must be a physical KI repository. With neither selector, KI checks a regular direct-CWD schema-one .mgit.toml manifest. A workspace manifest selects its configured group, recurses through child workspaces, follows standard and nested repositories, and skips bare stores. A repository manifest falls through to ordinary single-repository discovery. KI never searches ancestor directories for an mGit manifest or invokes mgit. Selection never resolves to no repository: every selector either selects at least one repository or fails with a message and a non-zero exit.
--estate
Select every repository in the registered estate. This is shorthand for --agora estate and is mutually exclusive with --repo and --agora.
Repository management
Use these commands to inspect and maintain declared capabilities and manage their skill links. Read-only operations isolate per-target diagnostics; a later mutation failure retains earlier successful targets and returns a non-zero result.
ki repo init [directory] --repository <https-url> --title <title> --description <description> --repo-code <code> --runtime <runtime>... --visibility <public|private>
Initialize exactly one existing physical Git worktree root. With no directory, it uses the current directory; an explicit directory must be that worktree's root and must not be a symbolic link. Every identity value is required: --title, --description, a stable uppercase --repo-code, canonical HTTPS GitHub --repository, one or more --runtime values selected from claude-code and chatgpt-codex, and --visibility public|private. It atomically creates the minimal canonical ki-repo declaration and registers the physical root in $XDG_STATE_HOME/ki/registry.toml. It never runs git init, guesses identity, activates repository skills, creates a Agora, accepts repository selectors, or overwrites an existing .ki.toml.
ki repo [repo-options] open --target <zed|vscode> [--stores|--no-stores]
Open every selected canonical repository in the requested local target. By default, a Knowledge Base that declares the sources store role opens its notes root followed by its locally registered sources root. The sources binding must be a direct directory recorded with the canonical repository; it is never made an estate member or Agora participant. --no-stores opens canonical notes roots only, while --stores makes the default explicit.
ki repo [repo-options] audit [--skill <skill>] [--progress <auto|always|never>] [--progress-style <single|multi>] [--reporter-levels <levels|all>]
Run the native read-only operations registered by each selected repository's declared capabilities. The host verifies every selected harness inventory and integrity-covered operation before importing it in process; it never dispatches repository-vendored runners. Progress defaults to auto, which follows the output stream's TTY state; always also renders deterministic progress in redirected output, and never suppresses it. On a terminal, progress is a compact receipt stream with one mutable activity row. Its moving bar means work is active; it does not estimate completion from item count or declared cost. Evidence-ready skills appear once with a full bar, then collapse to one timed evidence receipt before rubric results begin. Loading and the operation also finish as timed receipts, with total elapsed time on the operation receipt. Queued skills are not printed. Use --progress-style single to suppress temporary per-skill evidence receipts. Redirected --progress always output defaults to that single-row form. Progress also names the span in which a skill gathers its evidence, before any criterion runs, together with whatever stages and steps that skill reports inside it; a span of unknown extent shows activity and an elapsed clock rather than a completion estimate. Per-skill result rows name the assessed repository first and its supplying harness skill in brackets, and appear only for WARN, FAIL, or FIXED outcomes. Audit renders FAIL and WARN findings by default; --reporter-levels accepts a case-insensitive comma-separated selection from FAIL, WARN, FIXED, INFO, NOT_APPLICABLE, and PASS, or all. A clean repository summary reports PASS with its skill count. Diagnostic counters remain for WARN, FAIL, and FIXED outcomes.
ki repo [repo-options] conform [--skill <skill>] [--dry-run] [--progress <auto|always|never>] [--progress-style <single|multi>] [--reporter-levels <levels|all>]
Stage the same capabilities' safe writes, then apply them and re-audit. All selected initial audits must pass before the staged conform writes are published: a blocking finding aborts before publication, leaving every proposed conform write unapplied. Output labels proposed writes separately from writes applied after that gate; a dry run validates the complete staged write set and reports writes it would apply without changing the repository. This boundary does not include independent local registry updates; it also excludes later selected repositories, subprocess conforms, and rollback after publication has started. Publication refuses unsafe, changed, duplicate, or symbolic-link targets. Conform uses the same progress controls and reporter-level vocabulary as audit, names both the target and supplier for every skill, and renders FAIL, WARN, and FIXED findings by default while retaining every terminal per-skill result. Its second rubric pass is labelled re-audit. When no write or command was staged, conform reports that no re-audit is required and stops after the initial pass. For a local invocation it records each selected canonical root in the machine-local registry before evaluating findings. Registration is an inventory action, not evidence of conformance, so a failing repository remains available for later repair and bulk maintenance.
ki repo [repo-options] roadmap list [--horizon <horizon>] [--status <status>]
List canonical governed work items from every selected repository without changing their lifecycle. The framed text output names each selected repository, then groups items by horizon from now through unadopted triage and by lifecycle from done through draft, with identifiers breaking ties. --horizon and --status filter before rendering. A missing roadmap directory or malformed or unsafe item is an isolated diagnostic for that repository; other selected repositories still report, and any roadmap or trade diagnostic makes the command exit with status 1 after rendering the inventory. The command never creates, transitions, accepts, prunes, or repairs a work item. Generic promote and demote operations exclude the unadopted triage horizon.
ki repo [repo-options] roadmap stats [--stale-after <duration>] [--format <text|json>]
Report timestamp coverage and age and inactivity metrics for selected local roadmaps. Timestamp-free compatibility records remain readable and are reported as missing coverage. Multiple selected repositories add a selected-set aggregate. A positive stale duration uses seconds, minutes, hours, or days, such as 7d. Use --format json for a versioned machine-readable report.
ki repo [repo-options] roadmap prune [id]
Without an ID, delete every canonical work-item record whose lifecycle status is exactly done from the selected repositories. It leaves every other lifecycle status, non-canonical file, and peer repository untouched. If no selected repository contains a completed record, it reports that no record was pruned. With an ID, require exactly one selected repository and delete only that named completed record.
ki repo [repo-options] roadmap promote <id> [horizon]
Move exactly one selected repository's named work item one horizon toward now. With an optional destination horizon, move directly only toward now; the current horizon, a future-facing destination, and the now endpoint are errors. The command changes only the item's horizon frontmatter; moving from future also removes its required candidate marker.
ki repo [repo-options] roadmap demote <id> [horizon]
Move exactly one selected repository's named work item one horizon toward future. With an optional destination horizon, move directly only toward future; the current horizon, a now-facing destination, and the future endpoint are errors. The command changes only the item's horizon frontmatter; moving to future adds its required candidate marker.
ki repo [repo-options] educate [--skill <skill>]
Explain each selected repository's declared capabilities and their recommended maintenance actions without changing repository state.
ki repo [repo-options] diag
Report each selected repository's declared skills and compatible runtime projection health without changing repository or registry state. It returns a non-zero status when a declaration or projection is unrepairable.
ki repo [repo-options] repair [--dry-run]
Record each selected physical repository root in the local user register, then reconcile only missing, dangling, or stale KI-managed compatible projections. It never creates a declaration, adds an undeclared skill, overwrites foreign content, guesses a provider or runtime, or follows a symbolic declaration. --dry-run reports the same actions without changing disk state.
ki repo [repo-options] skill add <skill> [--replace]
Add a registered skill in each selected repository.
ki repo [repo-options] skill remove <skill>
Remove a KI-managed repository skill link and declaration from each selected repository.
ki repo [repo-options] upgrade
Refresh uniquely resolved harness providers declared by each selected KI repository. It changes neither user nor repository skill activation.
Registry management
Use these root-level commands to record and list canonical KI repository roots in $XDG_STATE_HOME/ki/registry.toml. Registry membership is an inventory, not a repository-operation or conformance verdict. The repository key names each record; each record holds a canonical HTTPS GitHub repository identity and physical checkout path.
ki registry [--repo <path-or-pattern>]... [--agora <name>] [--estate] add [--dry-run]
Record selected canonical KI repository roots in $XDG_STATE_HOME/ki/registry.toml without applying repository repairs. This explicit inventory action validates the selected root's declared canonical identity and preserves existing entries. It never searches outside the supplied target selection.
ki registry list
List physical KI repository roots explicitly registered in the machine-local registry, one absolute path per line. The command neither discovers repositories nor changes state.
Harness management
Use these commands to install, inspect, and remove compatible harness payloads in the user-managed KI environment. A configured private GitHub archive may declare auth = github-cli only with its matching commit-pinned https://codeload.github.com/
ki harness info <harness-id>
Inspect one user-installed compatible harness and its capability inventory without changing user state.
ki harness list
List compatible harnesses already installed.
ki harness install <harness-id>
Install a harness from which capabilities, such as skills and subagents, can be added.
ki harness reinstall <harness-id>
Replace one inactive installed Harness with a verified archive. The command refuses a Harness that supplies active user skills. A development-linked Harness must first be restored with ki dev local off
ki harness uninstall <harness-id>
Remove one non-canonical harness with only recognised payload directories. The canonical harness cannot be removed, and a harness that supplies active user skills cannot be removed. A successful removal deletes its identifier from [harnesses].ids.
Trades
Use these commands with repositories that declare the portable ki-repo-trades capability and are present in the local registered repository estate. They preserve repository authority: every mutation writes only the current repository, a typed reciprocal route grants visibility rather than acceptance or retention, and no command changes a peer roadmap or knowledge.
ki trade routes add <repository> --direction export|import --kind work|knowledge
Declare one local typed route to a canonical HTTPS GitHub repository. Repository identity remains the required repository value in the ki-repo table.
ki trade routes remove <repository> --direction export|import --kind work|knowledge
Remove one local typed route.
ki trade routes list [--estate] [--incomplete] [--table|--html]
List local typed routes with their registered-estate state. With --estate, list every valid registered repository declaration as lexical repository pairs. The left and right endpoint cells span the two directional rows, which show what each repository sends with a right or left arrow; a missing direction is shown as an em dash. The table adapts to the live terminal width, preserving the same pairs in a stacked narrow view. With --incomplete, show only routes that await reciprocity or have ambiguous peers. With --table, explicitly select that estate text renderer; it requires --estate. With --html, write that estate to the cache as a self-contained interactive network page and open it; it requires --estate and cannot be combined with --table. The page draws one arc per direction, so a reciprocated pair separates, and uses accessible vendored Lucide Hammer and Book Open marks for its route kinds; it opens with no network. Active typed directions determine each lane's capacity, target distance, spring, and width. Node influence combines route degree, a derived knowledgeislands/* organisation uplift, and an optional repository-declared [skills.ki-trades].map_bonus; these presentation values do not grant trade authority. Set KI_BROWSER_OPENER to override the platform opener.
ki trade routes check [repository] [--direction export|import] [--kind work|knowledge]
Check declared routes by kind. An export awaiting local receiver registration, receiver participation, or a reciprocal import awaits receiver activation; the equivalent import awaits sender activation.
ki trade subtypes add <subtype> --description <text>
Define one lower-case receiver-owned knowledge subtype in the current repository. The description records the receiver's meaning for the subtype.
ki trade subtypes list
List receiver-owned knowledge subtype definitions in the current repository.
ki trade subtypes remove <subtype>
Remove one receiver-owned subtype only when no local standing import still names it.
ki trade standing add <repository> --direction export|import --subtype <subtype>
Declare one local standing knowledge-intake direction layered on an existing ordinary knowledge route. An import subtype must be defined by the local receiver. The declaration remains inactive until the peer publishes the exact reciprocal direction and the receiver-owned definition is available.
ki trade standing remove <repository> --direction export|import --subtype <subtype>
Remove only the current repository's standing declaration. Historical committed provenance remains local evidence, but the removed declaration no longer authorises new captures.
ki trade standing list [--incomplete]
List local standing declarations and report whether each exact subtype relationship is active, awaiting ordinary route activation, awaiting reciprocity, ambiguous, or unknown to its receiver. With --incomplete, show only declarations that are not active.
ki trade standing check [repository] [--direction export|import] [--subtype <subtype>]
Check all local standing declarations or select an exact repository, direction, and subtype.
ki trade standing capture <repository> --subtype <subtype> --source-ref <commit:path#anchor> --capture <path#anchor>
From the receiver repository, append one marked ki-trades/standing-intake/v1 TOML provenance block to an existing local Markdown file. The command requires an active exact standing import, a full source commit, and a source path that resolves in the locally registered source checkout. It never writes to the source repository. Standing intake grants no roadmap, publication, implementation, acceptance, completion, Agora, or peer-write authority; use an itemized knowledge trade when the exact standing contract does not fit.
ki trade prepare <repository> --kind work|knowledge --observation unattended|receipt|decision|completion --title <title> --source-ref <reference> --context <text> --submission <text> --constraints <text>
Create one mutable preparation in the current repository when it declares the matching export route. The mandatory observation policy selects whether receipt, a terminal decision, or completion of adopted work is required before release; unattended requires no receiver follow-up beyond an observable receipt.
ki trade observe <trade-id>
Read one sender's committed mutable preparation without receiving or acting on it. Compare it with the commit last observed by this receiver, or show the full current contents when no usable earlier Git evidence exists.
ki trade submit <trade-id>
Freeze one local preparation and move it to the outbound submitted path.
ki trade abandon <trade-id> --yes
Remove one unsubmitted mutable preparation after explicit confirmation.
ki trade receive <trade-id> | --all [--yes]
Import one committed outbound submission into the current repository and record its source commit. The --all form previews every receivable submission and changes nothing unless --yes is also supplied.
ki trade list [--direction prepare|import|export] [--status <status>] [--kind work|knowledge] [--repo <repository>]
Read visible preparations, imports, and exports in the registered estate, including their observation policy, delivery and decision state, and cleanup eligibility.
ki trade show <trade-id>
Show every visible copy of a trade.
ki trade release <trade-id> | --eligible [--yes]
Remove one current-repository outbound submission only after its observation policy is satisfied. The --eligible form previews all eligible submissions and changes nothing unless --yes is also supplied.
ki trade prune <trade-id> | --eligible [--yes]
Remove one eligible current-repository inbound copy only after sender release is observable. The --eligible form previews all eligible copies and changes nothing unless --yes is also supplied.
Agora management
Named Agoras are declared portably by registered home repositories under [skills.ki-agora.homes.
ki agora list
List declared named Agoras and the registered estate.
ki agora audit [name]
Audit every declared Agora, one named Agora, or the registered estate without changing repository or registry state. Exit 0 when healthy, 1 when findings are reported, and 2 for an invalid or unknown explicit selector.
ki agora inspect <name> --target <zed|vscode> --workspace <selector>
Compare one explicitly selected local editor workspace with a resolved Agora. VS Code selectors are absolute physical .code-workspace files; Zed selectors are decimal workspace IDs. Read-only. Exit 0 for exact, 1 for drift or an unsupported source, and 2 for invalid selection or resolution.
ki agora show <name> [--verbose]
Show one declared Agora or the registered estate. The default lists member names; --verbose also shows canonical repository URLs and local paths.
ki agora roots <name> [--null]
Write absolute physical roots for machine consumption. The default format is newline-delimited. Use --null or -0 for pathnames that may contain line feeds.
ki agora open <name> --target <zed|vscode>
Open one declared Agora or the registered estate through an explicit local target.
ki agora reference set <repository> <checkout> [--dry-run]
Associate one owner-declared external reference with an explicitly selected absolute local Git checkout whose canonical origin matches. The operation never registers, clones, or mutates the referenced repository.
ki agora reference list
List machine-local external Agora reference associations.
ki agora reference remove <repository> [--dry-run]
Remove only the selected machine-local reference association.
Acquisition
Acquisition is action-first and adapter-driven. Installed Harness skills publish verified machine-readable adapter declarations; repository configuration enables them.
ki acquire list [--repo <path>]
List enabled, available, and invalid acquisition adapters with owning skill, actions, configuration, executable status, and activation guidance.
ki acquire import [--adapter <name>|--all] [--repo <path>] [--since <date>] [--until <date>] [--dry-run]
Run one selected adapter, every applicable enabled adapter, or infer the sole enabled adapter. Adapter-specific invocation properties require explicit --adapter. ChatGPT accepts --capture and --output. Granola accepts --refresh-transcripts.
ki acquire status [--adapter <name>|--all] [--repo <path>]
Report local authoritative checkpoints, in-progress journals, transcript states, and post-acquisition dispositions without contacting the provider.
ki acquire reconcile [--adapter <name>|--all] [--repo <path>]
Verify local checkpoint and disposed-document evidence without mutating provider or repository state.
ki acquire reset [--adapter <name>] [--repo <path>] [--source <identity>] [--component <name>] [--rebuild] [--confirm]
Preview a local adapter, source, component, or complete-rebuild reset. Mutation requires --confirm and never authorizes provider mutation. The Granola adapter uses only allowlisted read-only MCP operations. It enumerates complete global and folder identity evidence, revalidates mutable detail, reuses verified transcripts by default, records separate detail and transcript hashes, journals interrupted work atomically, and advances the authoritative checkpoint only after the selected generation verifies. It stages meeting Markdown beneath +/_ACQUIRE/granola/. Conflicting receiver mappings fail closed; acquisition never tags, edits, archives, deletes, or moves Granola data.
Development
Use these commands to switch Harnesses already present in the installed KI estate between their verified archives and independent local development checkouts.
ki dev local set <harness-id> <local-harness-path>
Validate the identity against the installed estate and remember it with the local checkout without changing the active payload or managed user-skill links. When the selected harness is the canonical harness, the checkout must contain the core bootstrap skill at skills/keystone/ki-bootstrap/SKILL.md and physical skills, subagents, and hooks payload directories.
ki dev local on [harness-id]
Enable selected local checkouts for development. KI replaces each selected Harness's complete active root with its checkout, so its metadata and payloads always have one source, records each identity and path below [locals], and reconciles its managed user-skill links to the local source on every run. An explicit Harness ID selects one source; omitting it selects all remembered sources.
ki dev local off [harness-id]
Remove each selected recognised local Harness root, reinstall its verified archive, retain its entry below [locals], and reconcile its managed user-skill links to the restored archive. An explicit Harness ID selects one source; omitting it selects all remembered sources.
ki dev skill rubric <skill> [--write]
Check or regenerate a skill's rubric catalogue.
Batch records
The manual's reference section does not carry this group. These entries come from its synopsis instead, which lists them with a shorter description and no statement of what the group is for. That is an omission upstream rather than a choice here, so the group is published with the note rather than left out.
ki batch prepare --item <id> [--item <id>...] --approved --authority-mode <reviewed-items|outcome> --expires-at <timestamp> --completion-target <awaiting-review|done> [--authority-evidence <text>] [--repo <path>]
Create one current canonical exact-set batch record from caller-supplied approval evidence and Ready work items in dependency order.
ki batch validate <record> [--repo <path>]
Validate a canonical batch record, its protected payload, expiry, run binding, repository identity, and named work items without writing.
ki batch run <record> [--repo <path>] [--item <id> --result <awaiting-review|done|parked|stopped> --baseline <commit|—> [--result-commit <commit>] [--exception <text>]]
Start the derived run or append one explicit caller-supplied item result. This command does not execute agent work or change roadmap lifecycle.
ki batch close <record> [--repo <path>] --completion-target <awaiting-review|done> --evidence-commit <commit>
Append structural closure evidence only after every named ledger result and canonical work item matches the approved all-item target. This command does not accept work.
What this page cannot tell you
An inventory says what exists, not when to reach for it. The commands that carry a real decision have a page of their own: the capability lifecycle for harness and skill, update and upgrade for keeping an installation current, local utility commands for the inspection surface, and the ChatGPT capture format for the one import adapter with a format of its own.
It also says nothing about exit codes, configuration file locations, or the environment variables ki reads. Those are in the same manual, under sections this page does not vendor, and man ki on a machine with the tool installed is the fastest way to them.