Factory Droid mit unbegrenztem Claude betreiben

Droid ist eine agentische CLI, die in einer Schleife plant, bearbeitet und neu versucht, sodass eine einzige Aufgabe viele Tokens bewegen kann, bevor sie fertig ist. Genau diese Last gewinnt ein pauschaler, unbegrenzter Claude-Plan — lass Droid bis zum Ende laufen und der Preis ändert sich nicht.

One config, no meter

Droid reads ~/.factory/settings.json. Add a customModels array and each entry defines one model the CLI can use. With an unlimited plan behind it, you set this once and stop thinking about per-run cost.

settings.json is the modern path; the legacy config.json lacks some of its features. Keep your unlimited setup here so every Droid session draws from the same flat-rate plan.

Because Droid is built to run long autonomous sessions, the one-time config and the flat-rate plan complement each other well. You configure it once, then leave the cost question behind entirely and let the agent work as long as the task demands. Configure once, forget the meter, and let the agent run is the whole shape of this setup. The long autonomous sessions Droid favours fit a flat rate perfectly, since their cost is otherwise the hardest to predict.

Describe the Claude model

Each entry takes model, baseUrl, apiKey, provider, and maxOutputTokens. Point model at a gateway id like claude-sonnet-4-5 and baseUrl at the unlimited gateway host.

Set maxOutputTokens generously. On metered billing people cap output low to save money; on unlimited you can let Droid produce full, complete responses because the cost is the same either way.

A higher maxOutputTokens matters for an agent that writes code, since a clipped response can cut off mid-edit and force another round to finish. With the cost concern removed you size it for complete outputs, which keeps the agent loop smoother and reduces wasted turns. Complete outputs mean fewer wasted turns, which matters more the longer a session runs. A response cut off mid-edit forces another round you would rather avoid, so a generous limit keeps the loop moving.

Use the anthropic provider

Set provider to anthropic for the gateway's native Messages surface. The other modes, openai and generic-chat-completion-api, target OpenAI-style endpoints; for Claude on the unlimited gateway, anthropic is the match.

Getting the provider right keeps the agent loop solid through long runs. You want it correct so an hours-long unlimited session never trips on a wire-format mismatch.

This is more important on unlimited precisely because you intend the sessions to be long. A provider mismatch that you might catch quickly on a short metered test could otherwise surface deep into an extended run, so it is worth confirming on a small task before turning the agent loose. A small confirmation run up front is cheap insurance against a mismatch surfacing hours in. A quick sanity check costs nothing on an unlimited plan, and it spares you a failed long run.

Key handling

Put your unlimited key in apiKey, ideally as ${AIPRIME_API_KEY} so the secret lives in the environment. ${VAR} expansion works in settings.json but not the legacy config.json, and apiKey must not be empty.

That one unlimited key backs every model entry and every Droid session for the plan's period. There is no separate meter per model to watch.

So if you keep both a Sonnet and an Opus entry, they share the single unlimited key and the single flat rate between them. Switching models never changes what you pay, which makes the choice purely about which model suits the task in front of you. Sharing one key and one rate across model entries makes switching purely a quality decision. Cost never enters the choice between Sonnet and Opus, so you simply pick the model the task deserves.

Let the agent loop run

In the CLI, switch models with /model. Keep a claude-opus-4-8 entry for the hardest tasks and, because the plan is unlimited, leave it selected without worrying about token cost.

This is where flat-rate really pays off: an agentic CLI that retries and explores would be unpredictable on metered pricing. On unlimited you point Droid at a hard task, let it iterate as long as it needs, and pay the same fixed amount.

It also frees you from the instinct to interrupt a long run to save money, which often produces worse results than letting the agent finish its plan. When a five-minute run and an hour-long run cost the same, you make that call on whether the work is done, not on what the next stretch of tokens would add. Judging a run on whether it is done, not on token cost, is the mindset a flat rate unlocks. You stop interrupting good work to save money.

// ~/.factory/settings.json
{
  "customModels": [
    {
      "model": "claude-sonnet-4-5",
      "baseUrl": "https://claudeapikey.dev",
      "apiKey": "${AIPRIME_API_KEY}",
      "provider": "anthropic",
      "maxOutputTokens": 8192
    }
  ]
}
// export AIPRIME_API_KEY=<key>   (apiKey must NOT be empty)
// Switch models in the CLI with /model

FAQ

Kann ich Factory Droid mit unbegrenztem Claude betreiben?
Ja — füge einen customModels-Eintrag mit provider anthropic, baseUrl {SITE} und deinem unbegrenzten Schlüssel hinzu. Der Pauschaltarif deckt jeden Lauf ab.

Warum ist unbegrenzt gut für Droid?
Droids Agentenschleifen planen, bearbeiten und versuchen erneut und bewegen hohes Token-Volumen pro Aufgabe. Pauschal-unbegrenzt hält die Kosten fest, egal wie lange ein Lauf dauert.

Welcher provider-Wert?
anthropic für die native Messages-Oberfläche. apiKey darf nicht leer sein; nutze ${AIPRIME_API_KEY} in settings.json.

Gibt es Token-Limits?
Keine Token-Limits während des Plans, nur Fair-Use-Ratenlimits, damit das Gateway schnell bleibt.