Models

Models

Overview

Every prompt, agent, and automation runs through a model. TSK-Auto is the default, and it resolves a model on every turn. A manual choice is optional.

This page explains how that routing works and how to override it. For the catalog of models you can pin, see Custom Engine.

   TSK-Auto            TSK rungs              Custom Engine
   ────────            ─────────              ─────────────
   Picks for you       You set the            You pin one
   every turn          trade-off              exact model

   no setup            Instant → Reasoning    15+ frontier models
                       fast ←→ deep           many providers
        │                    │                      │
        └────────────────────┴──────────────────────┘
                             │
                    same workspace, same token

Level	You choose	Best for
TSK-Auto	Nothing. Taskade routes each turn.	Almost everything. This is the default.
TSK rungs	A speed-to-depth trade-off	You know the job is quick, or you know it is hard
Custom Engine	One exact model	Comparing models, or one model suits the task
Infinity Mode	A team of agents instead of one turn	Long build-and-check work

TSK-Auto

TSK-Auto is the default on every surface. It carries a Recommended pill in the model menu and needs no setup.

Auto resolves a model on the server, once per turn. It reads the kind of work the turn represents and the plan the workspace runs on, then routes to a model that fits.

Two properties matter more than the specific choice:

Auto re-decides every turn. A build turn and a follow-up edit in the same conversation can land on different models.
Auto is not pinned to your workspace. Taskade re-points the Auto lane as models ship and retire, so you get the improvement with no rebuild and no migration.

That second property is why these docs do not name the model behind Auto. Any name printed here becomes wrong the next time the lane moves, and the lane moves on a schedule you do not control.

When to override Auto

Override it when you know something about the job that Auto cannot infer from the turn:

You know	Use
The job is trivial and you want it now	TSK-Instant
The job needs real planning	TSK-Thinking
You are comparing two models on one prompt	Custom Engine
The work is a long build that must check itself	Infinity Mode

An override applies only to the surface you set it on. Setting a model on one agent changes no other agent.

TSK rungs

A rung sets a trade-off, not a model. You tell Taskade how much thinking the job deserves, and Taskade maps that to a model for you. It is the middle ground between Auto, which decides everything, and Custom Engine, which decides nothing for you.

   TSK-Instant     TSK-Standard     TSK-Thinking     TSK-Reasoning
   ───────────     ────────────     ────────────     ─────────────
   fast edits      everyday         multi-agent      workflows and
                   tasks            planning         systems

   ◀─────────────────── faster        deeper ───────────────────▶

Rung	What it is for	Availability
TSK-Instant	Fast edits	Every plan, including Free
TSK-Standard	Everyday tasks	Every paid plan
TSK-Thinking	Multi-agent planning	Every paid plan
TSK-Reasoning	Workflows and systems	Business and up

Match the rung to the shape of the work, not to how important the work feels:

A one-line change to text that already exists is a TSK-Instant job. A deeper rung returns the same edit more slowly.
A normal build step or agent answer is TSK-Standard.
Work that holds several moving parts at once is TSK-Thinking. Planning a multi-step automation belongs here.
Work that produces a system rather than an answer is TSK-Reasoning.

A rung survives the catalog. When a provider ships a better model at the same trade-off, Taskade re-points the rung and your agent improves with no edit. A pinned model id does not move, so it ages.

Infinity Mode

Infinity Mode plans, builds, and checks work with a team of agents instead of a single turn.

It is a switch, not a model, and that is the part people get backwards:

It does not replace your model choice. It layers on top of it.
Turning it on does not move you off Auto or off a rung you set.
It carries no model of its own in the menu.

In the builder chat, toggle it from the row directly below Current Model in the model menu. Your existing selection stays where it was. The agent editor and the automation-step pickers do not offer this row.

Use it where the checking matters as much as the building. A multi-screen app is a good fit, because one broken flow makes the whole thing unusable. So is a build with dependent steps, where an early mistake compounds. For a quick edit, leave it off. The extra stages cost time and credits that a one-line change does not justify.

Infinity Mode is available on Max and Enterprise.

Bring your own key

To bill a provider account you control, connect it and add a provider step. Taskade supports OpenAI, Anthropic, Google Gemini, Groq, and OpenRouter accounts. The step runs on your key, and every step around it keeps working normally.

See Multi-model AI access for the setup.

Next steps

Browse the catalog in Custom Engine.
See how a run is metered in Model credits.
Build with the REST API or the Action API.

Model routing1

Custom Engine