Factory Droid 1.0 Review: Leaner Harness, Same Caps

Factory shipped Droid 1.0 on October 29, 2026, and the headline number is efficiency: Script mode alone cut cost 15% on Claude Opus 5.5, with the best head-to-head matchup reaching 24% below a rival harness. The catch that decides most buying decisions is unchanged — rolling usage limits and how much review work a faster harness creates.

What Factory Droid 1.0 actually ships

Factory Droid 1.0 is a harness release, not a new foundation model. Factory Droid remains a model-independent coding agent that wraps third-party and open models with its own prompts, tools, result handling, and execution loop, and version 1.0 changes that loop.

Droid 1.0 runs on Desktop, terminal CLI, and SDK, with the same agent available through web, Slack, Microsoft Teams, Linear, Jira, and headless droid exec for scripts and CI. Factory lists Script mode, its name for programmatic tool calling, as 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.

Model choice stays open. Users can pick models explicitly, use Factory Router for automatic selection, or bring their own keys and local endpoints such as Ollama, LM Studio, and vLLM via BYOK.

How programmatic tool calling works in practice

Programmatic tool calling means the model writes a JavaScript program instead of calling tools one at a time. That program runs in a sandbox without its own file, network, or system access, invokes tools as variables, filters and loops deterministically, and returns only the selected output to the model context.

Ordinary agent loops re-append raw outputs to context after each single call; Script mode filters them in code before they re-enter context. That keeps instructions sent once, batches hundreds of tool calls inside one model request, and size-caps printed output.

Two worked examples from Factory's frontier-harness research post (October 29, 2026) make the mechanism concrete:

Factory also replayed a unit-test fix on GPT-6.1 Sol: direct calls needed 10 model calls and 56.8 seconds, while Script mode needed 5 model calls and 41.6 seconds, with model-call time falling from 42.3 to 28.0 seconds. Programs wait up to 5 minutes before returning output so far, can continue in the background, and wake the model on completion instead of polling.

Terminal-Bench 4 head-to-head vs Codex, Claude Code, Cursor, Devin, OpenCode

Factory's Terminal-Bench 4 comparisons run the same models across harnesses between October 23–28, 2026. All figures below are Factory's self-reported claims, not independent verification, and absolute scores and dollar costs are not disclosed — only deltas.

Three methodology caveats matter before treating these deltas as buying proof. Factory counted some Devin tasks as passed when Codex passed them because Devin stopped to ask questions (averaging 4.7 tasks per trial, accuracy-only effect), estimated missing Cursor token usage from transcripts for two trials after mid-task reconnects, and some direct-call comparisons are modeled estimates rather than observed runs. Cursor was excluded from the GPT-6.1 Sol comparison because Factory says Cursor had no OpenAI-model access at test time.

Old September 2025 Terminal-Bench scores cited in earlier Droid coverage and harness benchmarks use a different task set and harness version, so they neither confirm nor refute the 1.0 deltas above.

The Agent Factory loop and the quiet engineering

Factory's frontier-harness post details the Agent Factory loop and the engineering below: intake new models, evaluate all models on the same tasks, trace failures, test each change across affected models, and gate release on engineer review across more than 20 models.

Per-model tuning is the reason Factory gives for the loop. One example: adding line numbers to every file read cut Opus cost 22% on one task at ~2 tokens per line, but raised cost 8% on GLM and 32% on Kimi, so Factory made line numbering opt-in rather than default.

The non-PTC changes target cache, prompt size, recovery, and startup:

• Prompt-cache preservation: appending newly discovered tools to the end of requests instead of the top lifted reuse to 98% typical input-from-cache over the seven days ending October 22, 2026, and 91.5% token-weighted reuse across 20.4 million production CLI requests.
• Base-prompt reduction: first-request input fell from 20,887 to 13,055 tokens (−37%) between versions 0.170.0 and 0.250.0, with tool definitions down 15,798 to 8,528 (−46%); up-front tool definitions dropped from 11 to 2 with on-demand loading.
• Bounded autonomy: 4 minutes of silence on Factory-managed Anthropic streams triggers retry, 3 turns with no visible output stops the loop, 3 identical tool calls nudge and 6 stop it, and compaction summaries doubled from 8,000 to 16,000 tokens.
• Startup and latency: median first paint 1,839 ms to 488 ms (~3.8x), prompt acceptance 1,876 ms to 618 ms (~3.0x), and time to first model request 1,741 ms to 646 ms, with Factory noting the model request itself is ~97% of first-token wait.

Pricing and limits where efficiency leaks

Factory Droid pricing is public; usable capacity is not. Plans are straightforward on price and opaque on quantity, which is exactly where the 1.0 efficiency gains can disappear.

Usage runs on 5-hour, 7-day, and 30-day rolling windows with model multipliers, and CodeToolPilot's October 2026 review notes the docs and pricing page have disagreed on which tier includes Droid Computers — confirm before buying. When Standard Usage exhausts, work falls back to the free Droid Core open-weight pool or prepaid Extra Usage ($10 minimum, non-expiring); Missions require Extra Usage enabled. BYOK keys live in local settings, work in CLI and Desktop but not hosted web/mobile, and are free up to a plan allowance before plan-rate billing.

The practical leak: a "5x" multiplier does not mean 5x completed work, because throughput depends on model choice, cache behavior, context length, tool loops, computer use, and failed trajectories. Heavy users on Reddit report burning the Max pool in hours on cache-unfriendly work, which Script mode mitigates but does not eliminate.

What real users are flagging right now

Launch-day sentiment on X is positive but thin, while longer Reddit history in r/FactoryAi surfaces three durable complaints worth pricing into a trial: quota opacity, slowness and CPU load, and review burden from autonomous output.

"If you are comparing usage then Droid's plan will most likely not be able to match the subsidized plans from Anthropic and OpenAI ... But as a harness I personally found it to be superior to Claude Code, in my useage it 'just works' (better system prompt perhaps), great spec mode, has all the necessary UX elements." — u/FahimAdib11, r/FactoryAi

Counter-reports in the same threads describe:

• Max-plan burnout in ~4 hours on caching-unfriendly runs ("It's really bad the caching is way off") — quota thread
• idle-CPU readings around 101% vs ~6% for Claude Code with MCPs suspected — performance thread
• session restarts that lose context and force wasteful re-establishment

Early X hands-on notes echo the split: one user porting a t3code-style Claude Code integration reports healthy usage on mission mode and calls the harness "next level" (@Davidwuuu92), while conceding Devin's cloud environment and multi-platform flexibility remain ahead.

The evaluation lesson from Continuum's Factory review still applies to 1.0: measure accepted changes, reviewer minutes, escaped defects, interventions, limit hits, and total cost — not sessions started or PRs opened — because autonomous throughput creates review debt.

Switch or stay? A buyer check plus a 2-week test

Droid 1.0 strengthens the harness-efficiency case without resolving the quota-predictability case. The buyers who gain most are teams that standardize one runtime across models, surfaces, and CI — and can absorb the review load.

Run a 2-week same-repo test before standardizing:

1. Pick 20 real tickets with fixed acceptance tests.
2. Run Droid CLI locally first, with Specification Mode on complex work.
3. Keep a Claude Code or Codex control on identical tasks.
4. Add remote execution, then one small Mission with deterministic validators.
5. Log every limit hit, Droid Core fallback, Extra Usage draw, reviewer minutes, and cost per accepted milestone, and reproduce one completed task on a clean machine to catch environment drift.

The trade-off 1.0 leaves open is structural: Factory bets the harness matters more than the model, tuning per-model behavior through the Agent Factory while staying model-independent. If frontier-model pricing or rate structures shift, today's 12–24% harness edge can shrink faster than any Script-mode batch can recover — which is why the contract terms on limits, retention, and routing deserve as much scrutiny as the benchmark table.

Factory Droid 1.0 FAQ

Is Factory Droid 1.0 worth the $20 Pro plan?

Factory Droid 1.0 is worth $20 for developers who run enough terminal-agent work to feel token and latency costs, especially multi-file or ticket-driven tasks where Script mode batches tool calls. Light or single-model users may find an already-included agent cheaper.

Does Factory Droid have a free trial or free tier?

Factory Droid lists no conventional free tier, and recent reviews note signup asks for a payment method. Paid-plan exhaustion falls back to the free Droid Core open-weight pool, but a paid plan is still required.

Is Factory Droid 1.0 better than Claude Code?

Factory's Terminal-Bench 4 claims Droid 1.0 scores 3.0–7.6 points higher than Claude Code on Claude Opus 5.5 at up to 24% lower cost and 26% less time per passed task. Those are Factory's self-reported figures; Reddit hands-on reports split between preferring Droid's harness and preferring Claude Code's friction and pricing.

Which models support Script mode by default?

Factory lists 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. Other models use direct calls or per-model tuning.

What are Factory Missions and what do they cost?

Factory Missions decompose large goals into milestones with worker and validator agents for multi-feature projects. Missions require Extra Usage to be enabled and consume prepaid variable spend on top of rolling Standard Usage.

Can Factory Droid run in CI and use my own keys?

Factory Droid runs headlessly via droid exec with JSON output for scripts and CI, and BYOK supports Anthropic, OpenAI, compatible endpoints, Bedrock, and local Ollama/LM Studio/vLLM in CLI and Desktop. Custom models do not work in hosted web or mobile apps.

Related reading: Codex usage limits explained for quota comparisons, and Microsoft Copilot harness explained for a second harness-design reference.