AgentConfigurationdowncity.json
services Configuration
Common service configuration patterns in an Agent project, especially chat channels
services Configuration
The services section declares agent-level service configuration for the project.
The most common case is chat
For example:
{
"services": {
"chat": {
"channels": {
"telegram": {
"enabled": true,
"channelAccountId": "telegram-main"
}
}
}
}
}For most users, this is also the first services block they will write.
What this does not mean
This is not where you store the Telegram bot token.
It only says:
- this agent enables the Telegram channel
- this project should bind to the city-level
telegram-mainaccount
So when chat entry does not work, the first things to verify are usually:
- whether the global channel account exists
- whether
channelAccountIdis correct - whether the agent was restarted after the change
Recommended mental model
- credentials live at the global level
- bindings live at the project level