2.13.0-beta.20). Features may change before the next stable release.Switch to stable →ak projects
ak projects list
Read every registered AgentKit project in deterministic canonical-directory order.
Use ak projects list to see which local directories the current user registry
knows about.
Usage
ak projects listThe command accepts no positional arguments and has no command-specific flags. Shared output flags are described in CLI conventions.
Examples
ak projects list
ak projects list --jsonRead the result
Human output shows a table with each entry's name, canonical absolute
directory, registration date, and updated date. Entries are sorted
deterministically by directory. An absent registry is a normal empty result and
exit 0.
JSON success uses kind=projects.list. Its data object contains total and a
projects array. Each array item contains name, dir, registered_at, and
updated_at. An empty registry produces total: 0 and an empty array.
--quiet suppresses all success stdout; it does not turn the table into a
headerless list.
Effects and privacy
The command only reads projects.json. It does not stat project directories,
verify AgentKit ownership, prune stale entries, contact a service, authenticate,
read a remote cache, prompt, or start another process. A listed path can be
stale even when listing succeeds.
Output contains absolute local paths and timestamps. Treat it as environment metadata before publishing logs or attaching JSON to an issue.
Exit status
| Exit | Meaning |
|---|---|
0 | The registry was listed, including an absent or empty registry. |
1 | The registry was unreadable, malformed, incompatible, or another read operation failed. |
2 | Arguments or flags could not be parsed. |
In JSON mode, command-level failures use an error envelope on stderr. Flag-parse failures can remain plain text.