kapi status

$ kapi status

Show, per target locale, how much of the project's tracked content is translated and whether it clears its ship gate, a derived dashboard, like git status. Coverage is recomputed from the content × target files on every run; nothing is tracked as state.

This is the informational counterpart to 'kapi check --ship' (the quality gate). It never fails: a locale that is behind is reported as pending rather than as an error. Target-language drift is normal, expected work rather than a build break.

Commandstatus

Groupwork

Try it

Runs in your browser against a small sample file. Edit the command before running, or press Run to execute it as shown.

$ kapi status

Flags

Flag	Type	Default	Description
--emit	string		with --ship, write the manifest to this path (e.g. ship.json) instead of stdout
--json	bool	false	output the structured result as JSON
--lang	stringSlice		with --review, list only these languages (repeatable, or comma-separated); the source language is one of them
--locale	string		limit to a single target locale
--project, -p	string		path to a kapi.yaml project recipe or its directory (auto-discovered from cwd if omitted)
--review	bool	false	list the units awaiting review in every language, the source language among them, instead of the coverage grid; approve a translated unit with `kapi apply` (kind:"review")
--ship	bool	false	emit the minimal ship.json picker manifest (locale → {shippable, verified, not_governed}) instead of the coverage grid; a language picker reads it to offer only shippable locales and to badge the unverified ones as AI-translated
--source-lang	string		source language (overrides the project's source_language)

← Back to the Command Reference