Skip to main content
September 9, 2026
The Model section of the DinoAI agent builder listing model presets with their relative cost, and the selected OpenAI preset showing its main, sub-agent, and planning models
Until now every DinoAI agent ran on the workspace’s default models. An agent can now be pinned to a model family: a named set that says which model does the main work, which runs sub-agents, and which handles planning.
  • In the builder. The Model section of the agent builder lists the presets configured for your workspace, each showing its three role models and its relative cost. Pick one and it is saved with the agent.
  • In YAML. Agents defined in your repo take a model_family: <slug> field, and the builder round-trips it, so the form and the YAML view stay in agreement. The older model: field is still accepted and still ignored.
  • Per run. The trigger mutation takes an optional modelFamily argument that overrides the agent’s own choice for that run.
  • Visible after the fact. A session’s header carries a chip naming the family the run actually used, with the three role models in its tooltip. The family is resolved once when the session starts, so editing an agent mid-run cannot move that run onto different models.
If a family names a model your workspace does not have, or an agent references a family that no longer exists, the run falls back to the default family and says so rather than failing. Workspaces with no families configured keep today’s automatic behavior. Shipped in Paradime v6.12.0.