city agent create

Usage

city agent create [path]
city agent create . --force

What it does

This command initializes an Agent project in the target directory and creates the minimum runtime scaffold.

Typical outputs include:

• PROFILE.md
• SOUL.md
• downcity.json
• .downcity/
• downcity.schema.json

It also tries to avoid pointless overwrites and surfaces next steps after initialization completes.

What the interactive flow asks for

The CLI currently asks for:

• Agent name
• primary model ID
• chat channels to enable

The two most important inputs are:

• project identity, such as the agent name
• execution target, especially the model ID

Main option

• -f, --force allow overwriting an existing downcity.json

When to use it

• the first time you turn a repository into an Agent project
• when a repo still has no Downcity runtime scaffold

What to inspect immediately afterward

1. downcity.json.execution.modelId
2. PROFILE.md
3. whether you really need chat channels enabled yet

If you are only validating the local runtime path, keeping the project minimal is usually the best first move.

A common misunderstanding

Do not read create as "set up all external infrastructure."

It creates:

• the project scaffold
• the minimum runtime shape
• the files needed for Downcity to recognize this directory as an Agent project

It does not automatically create:

• the global model pool
• global channel accounts
• every external platform integration

Continue with:

• Create your first Agent
• downcity.json basics