kapi info

$ kapi info [work.kpz]

With no argument, reports the project in scope: its languages, how many files it tracks, and the parts a kapi pack snapshot would capture — each with whether it is present and how many items it holds — plus what the snapshot deliberately leaves out (regenerable caches, credentials, sync tokens).

With a .kpz argument, reports that archive. A project snapshot is reported as the same parts, in the same words, so comparing the two is the round-trip check. A workspace .kpz (the ad-hoc parcel with a working cache) instead reports its documents, locales, and whether the cache holds work not yet packed back.

Both forms support --output-format json|yaml.

Commandinfo

Groupadvanced

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 info # the project: what a snapshot would capture

Flags

Flag	Type	Default	Description
--color	string	auto	colorize output: auto, always, never
--jq	string		filter JSON output through a jq expression (implies --json)
--json	bool	false	Output in JSON format
--output-format	string		Output format: text (alias: table), json, yaml
--project, -p	string		path to a kapi.yaml project recipe or its directory (auto-discovered from cwd if omitted)
--text	bool	false	Output in text format (default)

More examples

$ kapi info handoff.kpz # the archive: what it holds

← Back to the Command Reference