Key details

  1. Fusion became available in Devin Desktop and Devin CLI on September 11, 2026.
  2. The harness uses two persistent agents: a frontier lead for planning/review and a cheaper sidekick for execution.
  3. Cognition recommends Fable 5.1 as lead and SWE-2 as sidekick.
  4. In Cognition’s table, Fable 5.1 on DeepSWE 1.1 falls from 64.3 to 63.1 while reported cost drops from $14.63 to $7.88, a 46% reduction.
  5. Astra on DeepSWE 1.1 moves from 67.6 to 67.3 while reported cost drops from $7.88 to $4.69, a 40% reduction.
  6. Some workloads show larger quality trade-offs: Astra on Terminal-Bench 4 drops from 55.6 to 50.0 while cost falls 40%.
  7. Cognition’s published benchmark results are vendor-produced and should not be treated as independent validation.
  8. Fusion is an orchestration/harness change rather than a new standalone foundation-model release.

What builders should take away

  1. Measure coding agents by cost per acceptably completed task rather than token price alone.
  2. Benchmark the harness and model combination together; changing orchestration can alter both quality and cost even when the lead model stays the same.
  3. Use expensive models selectively for planning, review and difficult decisions if cheaper execution models can reliably carry out bounded work.
  4. Track retry, review and correction costs. A cheaper first pass can be more expensive overall if quality loss creates extra human or agent loops.
  5. When comparing vendor benchmarks, inspect per-workload regressions instead of relying on an average efficiency headline.
  6. Persistent role-specific contexts may be worth testing when repeated cross-model context transfer is consuming tokens or degrading cache efficiency.

What changed

Cognition released Fusion in Devin Desktop and Devin CLI on September 11, 2026. Rather than running one model for an entire coding task, Fusion keeps two persistent agents: a stronger frontier “lead” handles planning and review, while a cheaper “sidekick” performs much of the implementation work. The agents maintain separate contexts and exchange briefs, results and feedback, which Cognition says preserves prompt-cache efficiency while moving a large share of execution tokens onto the cheaper model. Cognition recommends using Fable 5.1 as the lead with its SWE-2 model as the sidekick.

Why it matters

Coding-agent economics are often discussed as model price per million tokens, but a harness can change which model consumes those tokens and how much rework a task needs. Fusion makes that orchestration strategy a product feature. In Cognition’s published tests, the two-model setup usually cut total task cost substantially while keeping benchmark scores near the single-frontier-model baseline, although several workloads lost measurable accuracy. For teams running agents heavily, that makes harness design and task-level cost as important as nominal model pricing. The trade-off is that these are Cognition-run benchmarks rather than independent production measurements.

The expensive model becomes a supervisor rather than the sole worker

Fusion assigns planning, review and higher-level decision-making to the lead model while the sidekick handles more of the execution. Both agents persist through the task instead of invoking a cheap model as a stateless one-off tool, so each can accumulate its own working context.

Cognition reports large cost reductions, but not free accuracy

Across Cognition’s published benchmark table, Fusion reduces reported task cost by roughly 11% to 46% depending on the lead model and benchmark. Some scores remain almost unchanged or improve slightly, while others fall—for example Astra on Terminal-Bench 4 drops from 55.6 to 50.0 and on the Vals Code Migration benchmark from 67.7 to 61.3. That makes the result a cost-quality trade rather than a universal efficiency win.

Task economics can invert raw token-price assumptions

Cognition argues that the cheapest model per token is not necessarily cheapest per solved task. Its FrontierCode example reports Astra Fusion with SWE-2 at $2.34 and a 63.4 score versus a cheaper-per-token Luna sidekick at $2.39 and a 62.0 score. The useful metric therefore becomes total cost for acceptable task completion, not the model’s list token price in isolation.

Persistent separation may preserve context and caching better than ad-hoc routing

The lead and sidekick maintain distinct contexts and communicate through explicit briefs, results and feedback. Cognition says this allows each role to keep a coherent prompt history and prompt cache rather than repeatedly moving a whole large context between models.

The evidence still needs independent validation

The benchmark suite, configurations and cost calculations are published by Cognition, which also sells Devin and provides SWE-2. They are useful engineering evidence but not neutral measurement. Production teams should test their own task mix, especially workloads where a small quality loss can create expensive review or retry loops.

Timeline

2026-09-10

Cognition introduces SWE-2

Cognition releases SWE-2 for coding work inside Devin, creating the lower-cost model later recommended as Fusion’s sidekick.
2026-09-11

Fusion launches in Devin Desktop and CLI

Cognition publishes the two-agent lead/sidekick architecture and benchmark results for the new harness.
2026-09-14

Independent coverage surfaces the cost architecture more broadly

Follow-on reporting highlights Fusion’s multi-model execution design and the gap between raw model pricing and task-level economics.

What to watch next

  • Independent replications of Fusion’s benchmark and task-cost claims.
  • Whether Cognition exposes more control over lead/sidekick model selection and role boundaries.
  • Production evidence on retry rates, review load and long-running-task reliability.
  • Whether other coding-agent vendors adopt persistent supervisor/executor pairs rather than single-model or per-turn routing.
  • Pricing and access changes for SWE-2 outside Devin, if Cognition broadens availability.

Still unclear

  • Cognition’s benchmark results are first-party and may not generalise to other repositories, task distributions or review standards.
  • Reported cost depends on the tested model prices, token usage and harness configuration at the time of the benchmark.
  • Several benchmark combinations lose accuracy, so the economic gain depends on how a team values failed, retried or manually corrected tasks.
  • The public evidence does not yet establish long-term production savings across independent customers.

Sources

Direct reading behind this dossier.

2 sources
Introducing Fusion in Devin Desktop & CLI
Cognition primary release announcement and benchmark

Primary description of Fusion’s lead/sidekick architecture, availability, model recommendation and benchmark cost/quality results.

Discussion

Discussion is reader-contributed. Comments are not part of the BTN dossier or its editorial evidence.

0 visible comments

Join the discussion

Keep comments useful and relevant. Reader contributions may be moderated and are not BTN editorial evidence.

Sign in to comment