CLI
City manages local Agents; Fed manages Federation Servers
CLI
The Downcity package installs two independent tools:
city(aliasdowncity) is the local City container for Agents, plugins, environment variables, and Federation connections.fed(aliasdownfed) is the Federation Server Manager. Its TUI manages registered servers,fed webstarts the local Web control plane, and project commands readfederation.jsonfrom the current project.
City data model
An Agent is a global entity identified by agent_id; its Workspace path is only a mutable binding. Agents, plugin bindings, and tokens live in ~/.downcity/downcity.db. Global Env lives in ~/.downcity/.env, Workspace Env lives in the project .env, and daemon files live in ~/.downcity/runtimes/<agent_id>/.
Plugin artifacts are installed globally under ~/.downcity/plugins/. Plugin configuration is not stored on the Agent SDK runtime Plugin object. It is stored per agent_id + plugin_name in an Agent Plugin Binding.
City commands
| Command | Purpose |
|---|---|
city agent | Manage global Agents |
city plugin | Manage plugin artifacts, bindings, config, and actions |
city env | Manage environment variables injected by City |
city federation | Manage Federation connections |
city init, city update, and city config are no longer provided. Upgrade globally with npm i -g downcity@latest.
Every command that operates on one Agent targets an agent_id. If omitted in a TTY, City opens the global Agent selector. Non-interactive calls fail with Agent ID is required; the current directory is never used for inference.
Platform support
The CLI architecture is cross-platform. macOS and Linux are stable targets; Windows adapters are currently preview quality.
Continue with CLI commands.