CLISpec) installed on the
workspace by name and separate from the mounts: an account CLI
initializes from its own config, consults no mount, and takes no operand
path. git is the credential-free tier, so it takes no config at all and
reads the repository -C names through the mount ops. The shell
dispatches a line to a CLI when its first word matches an installed
name.
clis: section:
--help, unknown verbs fail with git’s
wording (exit 1), and missing required flags fail with argparse’s
wording (exit 2). Two installs under different head words are two
accounts.
Authoring your own CLI
The custom CLI authoring guide covers the complete lifecycle: a runnable multi-account example, typed and script CLIs, code and YAML registration, constructor validation, snapshots and credentials, theCLISpec / Option / Operand reference, and an agent authoring checklist.
Installed CLIs are self-discovering through man, --help, type, and
which. Installation remains a host-side API, so an agent can use and inspect
the programs it was given but cannot uninstall them.
Builtin CLIs
Reading stays on the mount (
cat, grep, jq over the virtual
files); acting goes through the CLI. The mounted tree’s
<name>__<id> path segments supply the IDs the CLI flags take.