AgentConfigurationModels
Platform Model Pool
Understand the relationship between the city global model pool and Agent project binding
Platform Model Pool
An Agent project does not store the full model definition by itself.
Where the model pool lives
The model pool belongs to the city global layer.
From a user perspective:
- the global layer stores the provider, model name, API key, and other full model details
- the project only stores
execution.modelId
That is why you usually do not see the full provider configuration inside the project itself.
Why this design helps
- multiple projects can share the same model definition
- API keys do not need to be duplicated into every project
- switching models at the project level only changes one binding field
If you maintain multiple projects, this becomes very valuable quickly.
Typical workflow
- Prepare a model in the city global layer.
- Bind the project's
execution.modelIdto that model.
After that, switching models is mostly just switching the modelId.