Skip to content

Models, planning, delegation

The cheapest model per token is not always the cheapest per result, and jumping straight to code with the wrong approach wastes whole sessions.

VS Code language model selection dropdown VS Code thinking effort submenu
Choose a model (left) and its thinking effort (right). Source: VS Code Docs — Language Models.
  1. Choose models on evidence. Define the expected result and how you will judge it; run each candidate more than once (output is nondeterministic); compare completion, quality, reliability, duration, and credits; pick the cheapest model that consistently meets the bar. Re-evaluate as models change.
  2. Low-maintenance default: use auto model selection. For repeatable workflows, pin a model in a custom agent.
  3. Leave thinking effort at defaults. Higher effort produces more thinking tokens (cost and latency). Raise it only for genuinely complex work such as architectural planning or multi-step debugging.
  4. Plan, then implement. Use the Plan agent with a capable model, review the plan, split it into well-scoped tasks, and delegate those to custom agents as subagents with cheaper models, focused instructions, and minimal tools. The primary agent reviews results.

A simple approximation is total cost = rate × calls × accumulated context (where accumulated context is the average tokens per call). For a synthetic comparison, a model with one-third the token rate that makes four failed test-loop calls and then succeeds uses at least 1/3 × 5 of the frontier model’s one-call cost if their average context is equal; growing tool outputs can increase it further. Real bills also distinguish input, cached input, and output rates. Compare models at the same task success and include retries, tool outputs, and any final successful run.

For a recurring task type, compare (a) one strong model end-to-end against (b) plan with a strong model + workers on a cheaper one. Record credits, retries, and whether the result passes your acceptance check.

  • Delegation itself uses tokens. Keep small tasks in the main session if isolation and a cheaper model do not offset the orchestration overhead.
  • A cheaper model that needs retries or creates rework can cost more overall.

Ordered by venue tier, then citations. Findings are hypotheses to verify on your own workload; see the full list in Papers.