Dokki uses a live model catalog for Copilot, agents, and generation workflows. The active catalog is stored in Dokki's ai_models settings and served to the client from /api/models; code carries a bootstrap fallback so the picker is never empty during startup or a catalog read failure.
Model catalog
The production database catalog is authoritative for which models are enabled, their access band, display order, default model, and usage rates. Dokki keeps a bootstrap catalog only as a temporary fallback if the database catalog cannot be loaded. Because the catalog can change independently of this guide, use the model picker for the current list.
Auto routing
The model picker includes Auto. Auto is not sent to a provider. It is a sentinel that the chat API resolves to a concrete in-plan model for each request.
Auto routing looks at the latest user turn:
Signal | Effect |
|---|---|
Short/simple text | Prefer a fast low-cost model. |
Longer text | Move toward a mid-strength model. |
Code, debugging, architecture, analysis, or complex reasoning keywords | Prefer a stronger model. |
Image attachment | Prefer a vision-capable model when the plan and org allow it. |
Auto also respects the current plan and organization model allowlists. It does not use a model that has been disabled or removed from the catalog. Auto works for both Copilot and agent runs.
Model tiers
The picker groups model access into AI Basic Models, AI Pro Models, and AI Max Models. The plan gate is enforced server-side even if the client picker has stale data.
The client picker shows locked models when they are above the user's plan. In organization context, it also filters the picker by the organization's allowed model list when one is configured.
Vision models
Image understanding is limited to models marked as vision-capable in the active catalog. If the selected model cannot read an attached image, choose a vision-capable model shown in the picker or use Auto. Do not rely on one named model always being available.
Credits and limits
Each completed turn calculates credits from input/output tokens and the active model's catalog rates. If the catalog lookup fails during billing, Dokki uses a conservative fallback rate rather than treating the turn as free.
Plans can impose daily and weekly usage windows. Extra Usage can continue after included limits when enabled, until credits or the configured cap runs out.
Organization controls
Organizations can restrict available models with an allowlist. An empty allowlist means members may use any model their plan permits. A non-empty allowlist narrows the model pool for organization workspaces and also constrains Auto routing.