downcity.json Basics

downcity.json is the main configuration entry for an agent project.

Minimal example

{
  "name": "my-agent",
  "version": "1.0.0",
  "execution": {
    "type": "api",
    "modelId": "quality"
  },
  "services": {}
}

Fields you will usually edit

• name
• execution.modelId
• services.chat.channels.*

If you keep only those fields healthy, that already covers most day-to-day agent usage.

What this file is responsible for

Its main job is to:

• declare the project name
• declare which global model the project should use
• configure project-level services
• bind channel accounts

From a user perspective, the most important job of downcity.json is not "store everything." It is "declare how this project should be assembled at runtime."

What should not live here

• the full global model pool definition
• global bot credentials
• console-level control plane settings

Those are not single-project agent settings.

Once those concerns get mixed into downcity.json, it becomes harder to tell:

• what should move with the project
• what should stay global

Continue reading

• Execution binding
• Service configuration