kapi ls

$ kapi ls [path...]

List the files matched by the project's content collections (honoring the exclude list). With --stats, also show per-file block and word counts.

--untracked inverts the question: the files kapi can read that NO collection tracks. That is what a surface added since the recipe was written looks like: governed by nothing, and invisible to every listing that starts from the collections. Review it and declare what belongs; like an untracked file in a version-control status, it is reported and never adopted.

In a server-connected project (a recipe with a bowrain: block, with the bowrain plugin installed) a SYNC column reports each file's pending-push standing ("2 to push" / "synced"), derived from the sync cache.

kapi ls kapi ls src/ kapi ls --stats kapi ls --untracked

Commandls

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 ls

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)
--stats, -s	bool	false	show per-file block and word counts
--text	bool	false	Output in text format (default)
--untracked	bool	false	list readable files no collection tracks

← Back to the Command Reference