Quick Start

Connect your first project to Downcity through one shortest path.

Do not build a control plane first and do not rewrite workflow first. Start from the repo you already run. In five steps, the folder becomes a durable agent operating block.

Start from one real repository, not a demo project.Close one minimal loop before adding approvals, skills, or extra channels.If multiple people operate the system, define folder boundaries before role split.

Install the CLI

Establish one local runtime entry point first. Installing exposes the `downcity` command (alias `city`).

npm install -g downcity
downcity --version

Create the agent inside your repo

Initialize inside a real project so rules, permissions, and artifacts stay in the repo instead of a separate platform.

cd /path/to/your-repo
downcity agent create .

Connect City and start runtime

Import the active City session into downcity, then start the runtime. Use foreground mode only when you need live logs in the current shell.

downcity federation use
downcity start
downcity agent start
# for debugging
downcity agent start --foreground

Select the Session model

After the Agent starts, select a Federation model for the current Session. The choice is stored with Session runtime data and applies on the next turn without restarting the Agent.

downcity agent model .
# SSH or automation
downcity agent model . --session-id <session-id> --set <model-id>

Run a health check

Verify runtime state first, then add skills, channels, and scheduled tasks. Boundaries before expansion.

curl http://localhost:3000/health
curl http://localhost:3000/api/status

Continue in the docs

Once the five steps are working, move into the full quick-start guide and connect configuration, skills, and automation.

Read Full Quick Start Back Home