Agent¶
The agent configuration defines the core settings for your Datus Agent, including the target model selection and all available LLM providers that can be used throughout the system.
Configuration Structure¶
Target Model¶
The target field specifies the default LLM configuration that will be used across all nodes unless explicitly overridden.
Models Configuration¶
Configure LLM providers that your agent can use. Each model configuration includes the provider type, API endpoints, credentials, and specific model names.
Required Parameters per provider entry:
- Provider key (
models.<key>) - Logical provider identifier, referenced byagent.targetand nodemodelfields (you can name it as needed) type- Interface type corresponding to LLM manufacturersbase_url- Base address of the model provider's API endpointapi_key- API key for accessing the LLM service (supports environment variables)model- Specific model name to use from the provider
agent:
target: provider_name
models:
provider_name:
type: provider_type
base_url: https://api.example.com/v1
api_key: ${API_KEY_ENV_VAR}
model: model-name
Environment Variables
Use environment variables to securely store API keys and other sensitive information:
Supported LLM Providers¶
Providers selected in datus-agent configure are written into agent.models, and agent.target points to the default one. In practice:
- The provider name you choose in
datus-agent configurebecomes the key underagent.models.<provider> - You can later edit
agent.ymlmanually and bind different nodes to different model entries
General-purpose providers¶
| Provider | Typical models | Interface Type | Auth |
|---|---|---|---|
openai |
gpt-5.2, gpt-4.1, o3 |
openai |
API key |
deepseek |
deepseek-chat, deepseek-reasoner |
deepseek |
API key |
claude |
claude-sonnet-4-5, claude-opus-4-5 |
claude |
API key |
kimi |
kimi-k2.5, kimi-k2-thinking |
kimi |
API key |
qwen |
qwen3-max, qwen3-coder-plus |
openai |
API key |
gemini |
gemini-2.5-flash, gemini-2.5-pro |
gemini |
API key |
minimax |
MiniMax-M2.7, MiniMax-M2.5 |
minimax |
API key |
glm |
glm-5, glm-4.7 |
glm |
API key |
Special-auth providers¶
| Provider | Interface Type | Auth | Notes |
|---|---|---|---|
claude_subscription |
claude |
Claude subscription token | The wizard first tries to auto-detect a local subscription credential and otherwise prompts for sk-ant-oat01-... |
codex |
codex |
OAuth | Uses locally available Codex OAuth credentials and verifies connectivity |
Coding Plan providers¶
These providers target coding/planning-oriented endpoints. Even though their names include coding, they are configured exactly like any other model entry and can be used as agent.target or referenced from node-level model fields.
| Provider | Default model | Interface Type | Notes |
|---|---|---|---|
alibaba_coding |
qwen3-coder-plus |
claude |
DashScope Anthropic-compatible coding endpoint |
glm_coding |
glm-5 |
claude |
GLM Anthropic-compatible coding endpoint |
minimax_coding |
MiniMax-M2.7 |
claude |
MiniMax Anthropic-compatible coding endpoint |
kimi_coding |
kimi-for-coding |
claude |
Kimi coding endpoint |
When to choose a coding plan provider
If your priority is general chat, SQL generation, or cost efficiency, start with a regular provider.
If you want a default model that is better aligned with planning, code generation, and structured task decomposition, or if you use Plan Mode frequently, add one of the *_coding providers and route specific nodes to it.
Environment variables and model overrides¶
All providers support environment-variable references in api_key, for example:
For OpenAI, DeepSeek, Claude, Kimi, Qwen, and Gemini, the configuration wizard can prompt with provider-specific environment variable hints. For minimax, glm, and the *_coding providers, you can still enter values such as ${MINIMAX_API_KEY}, ${GLM_API_KEY}, ${KIMI_API_KEY}, or ${DASHSCOPE_API_KEY} directly.
The current implementation also auto-applies fixed parameter overrides for a few models:
kimi-k2.5:temperature: 1.0,top_p: 0.95qwen3-coder-plus:temperature: 1.0,top_p: 0.95
Provider Configuration Examples¶
Complete Configuration Example¶
Here's a comprehensive agent configuration example with multiple providers:
# Complete Datus Agent Configuration
agent:
target: alibaba_coding
models:
openai:
type: openai
base_url: https://api.openai.com/v1
api_key: ${OPENAI_API_KEY}
model: gpt-5.2
gemini:
type: gemini
base_url: https://generativelanguage.googleapis.com/v1beta
api_key: ${GEMINI_API_KEY}
model: gemini-2.5-flash
claude:
type: claude
base_url: https://api.anthropic.com
api_key: ${ANTHROPIC_API_KEY}
model: claude-sonnet-4-5
deepseek:
type: deepseek
base_url: https://api.deepseek.com
api_key: ${DEEPSEEK_API_KEY}
model: deepseek-chat
alibaba_coding:
type: claude
base_url: https://coding-intl.dashscope.aliyuncs.com/apps/anthropic
api_key: ${DASHSCOPE_API_KEY}
model: qwen3-coder-plus
temperature: 1.0
top_p: 0.95