AgentConfigurationdowncity.json

downcity.json Examples

Common Agent project configuration examples

`downcity.json` Examples

Minimal project

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

Good for:

validating the startup path for the first time
narrowing the scope during troubleshooting

Bind Telegram

{
  "name": "my-agent",
  "version": "1.0.0",
  "execution": {
    "type": "api",
    "modelId": "quality"
  },
  "services": {
    "chat": {
      "channels": {
        "telegram": {
          "enabled": true,
          "channelAccountId": "telegram-main"
        }
      }
    }
  }
}

Good for:

when you already have a global Telegram account
when you want to verify a single chat channel first

Bind multiple channels

{
  "services": {
    "chat": {
      "channels": {
        "telegram": {
          "enabled": true,
          "channelAccountId": "telegram-main"
        },
        "feishu": {
          "enabled": true,
          "channelAccountId": "feishu-main"
        }
      }
    }
  }
}

It is usually easier to get one channel working first and then expand to multiple channels.

services Configuration

Common service configuration patterns in an Agent project, especially chat channels

PROFILE.md

Use PROFILE.md to define the agent's role, output style, and behavior boundaries

Table of Contents

downcity.json Examples Minimal project Bind Telegram Bind multiple channels