Unify runtime and control plane
Keep CLI, daemon, Console gateway, and platform capability flow inside one city runtime model instead of splitting operations across separate surfaces.
Product · City SDK
Integrate the city runtime, CLI, control plane, and capability platform into one operating surface for your workflows.
Open City SDK Docs
Quick start, CLI, configuration, plugins, and operations live in the main docs.
Organize operations around the repo
Let configuration, commands, plugins, tasks, and state all follow one repo-native city structure.
Keep local and team deployment aligned
Use the same city entry surface for local validation, Console exposure, channel access, and production operation.
Typical Scenarios
- • Team runtime entry: start city, Console, channels, and plugins from one operating surface.
- • CLI-driven operations: create, start, reload, and inspect agents through one command layer.
- • Platform integration: host model, task, contact, memory, and shell capabilities inside your own deployment boundary.
Facts
- • Package name: downcity
- • Core source directory: cli/city/
- • CLI commands: city / studio