Skip to main content
Every task runs on one model tier, chosen at start with version and fixed for the life of the task.

Choosing a tier

Reach for scout on bounded, well-specified work where latency matters more than depth, wren when cost matters most and the brief already names the columns and constraints, and stay on ranger for open-ended research. wren is currently limited to admin plans. On any other plan it is rejected with 403 and {"error": "forbidden"}, so treat scout as the cheapest generally available tier. A well-specified prompt is what makes scout and wren viable; see Writing task prompts.

The tier is fixed at start

version only applies to the start routes. /task/{task_id}/continue and /task/{task_id}/execute stay on the tier the task started with. Read the tier back from GET /task/{task_id} as tier. ranger, scout and wren are the only accepted values; anything else is rejected with 403 and {"error": "forbidden"}. wren returns the same 403 on a non-admin plan, with the message tier 'wren' requires an admin plan.