Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

Factory Droid 1.0 and the harness-efficiency claim

Written November 4, 2026

Factory's harness cut prompt tokens 37% and reports fewer model calls than direct tool use. All figures are the vendor's; verify first.

What changed

Factory introduced Droid 1.0 on 29 October 2026 as the largest update yet to its coding-agent harness — everything around the model: the prompts, the tools, how tool results return, and the loop that runs it all. Droid is model-independent: it tunes its prompts, tool descriptions, and tool-calling mode for each model it supports, including models used with a user's own API keys. The headline change is programmatic tool calling, now the default, implemented as a Script tool. Script mode is on by default for GPT-6.1 Sol, GPT-6.1 Terra, GPT-6 Astra, GPT-6 Sol, GPT-5.6 Sol, Claude Fable 5.1, Claude Fable 5, Claude Opus 5.5, Claude Opus 5, and Kimi K3.

How Script mode works

Instead of calling tools one at a time and waiting for each result to return to the model, the model writes a JavaScript program that runs in a sandbox with no file, network, or system access of its own. A single Script can make hundreds of tool calls in one model request, so the instructions and history are sent once rather than re-sent every few calls. Raw tool results stay inside the program as variables; only printed output, capped in size, returns to the model, and the full results are logged where the model can search them later. Calls that do not depend on each other run concurrently. Factory's reasoning is that checks and loops then run deterministically in code, so a planned case cannot be quietly dropped mid-task.

What Factory reports

Every figure in this section is Factory's own, from its own sessions, telemetry, or benchmark runs. None of it has been independently reproduced, and the direct-call comparisons in the two worked examples are Factory's estimates, not measured runs.

Bounded autonomy

Long runs get stuck, repeat work, or drop the task, and Droid puts the recovery rules in the loop rather than in the model, so they hold for every supported provider. Three identical tool calls get a nudge and six stop the loop; three turns in a row with no visible output also stop it, while repeats that return new results, such as polling a build, can continue. When a long conversation is summarized, the compaction summaries now have room for 16,000 tokens, up from 8,000, because Factory estimates a third or more were filling the old limit.

How the harness is tuned

Factory's internal Agent Factory loop is part of the claim: agents study benchmark failures alongside friction from real sessions, propose changes, and test each one in a controlled experiment on every model family it affects. Engineers review the evidence and decide what ships. That loop produced Script mode and the per-model choice of whether to use it, and it keeps producing most of Droid's changes. A builder reading the efficiency figures should read them as the output of that loop — tuned against the same benchmarks used to report the gains — not as a neutral measurement.

What to do

Limits

Related playbooks

Sources

Back to: Coding playbooks hub · Also: Cut coding-agent costs with TokenEconomizer · BrokenML: a benchmark of broken machine-learning jobs