All fixes · Roo Code · Quota & billing

Roo Code API costs too high? It shut down, so cut costs in Cline or ZooCode (2026)

Roo Code API costs too high / too many tokens

Roo Code was shut down on May 15, 2026 and its repo is archived, so the lasting fix for Roo Code API costs is to move to a maintained agent and cut costs there: ZooCode (the community fork that keeps Roo's modes) or Cline (the agent Roo was forked from) both work with the same OpenAI-compatible backends. The cost profile carries over: whole files read into context and loops that re-send the growing conversation every step, so daily use on frontier models commonly lands at $60–200+/month per-token. The tactical fixes are context discipline and cheaper models for routine steps; the structural fix is a subscription-style backend: a coding-plan quota or a flat-rate endpoint.

What causes it

  • Whole-file context: Roo includes full file contents per mention, so large files balloon every request, the same dynamics as Cline.
  • Plan/Act loops re-enter tool results into context, so a 40-step task costs 40 increasingly large requests.
  • A frontier model doing routine Act steps (mechanical edits, running commands) that a budget model handles fine.
  • Modes and auto-approved retries multiplying request volume quietly in the background.

How to fix it

  1. Context discipline first: mention specific files instead of folders, use .rooignore for build artifacts and lockfiles, and start a new task per feature instead of one endless session.
  2. Split models per mode: a cheap model for routine Act/edit steps, frontier only for architect/planning and hard reasoning. Roo's per-mode model settings make this natural.
  3. Move off Roo before anything else: the extension gets no fixes or new model support since its May 2026 shutdown. ZooCode keeps the modes and settings model; Cline is the maintained original.
  4. Coding-plan quotas are the budget route: GLM coding plans and similar OpenRouter-adjacent subscriptions give a large monthly quota of open-weight usage for a few dollars, which is good if open models cover your work.
  5. For frontier models daily with no windows: point the OpenAI-compatible provider in Cline or ZooCode at a flat-rate endpoint so the meter stops mattering.

Running an agent? Everything that's true of Cline's costs was true of Roo's: the fork changed the UX and modes, not the token economics, so moving to Cline or ZooCode keeps the same levers. The biggest single lever is still file selection: one huge file mentioned across a long task can dominate the whole task's cost.

What it costs to run Roo Code

Keep working on a fixed monthly plan

Cline, ZooCode and the last Roo Code build all speak to any OpenAI-compatible provider: set the base URL to https://api.stdcmpt.com/v1, model standardcompute, and the agent runs on a flat monthly price (from $19/mo) with smart routing sending routine steps to budget models and hard ones to frontier models: no token meter, no 5-hour or weekly windows.

Plans from $19 a month with $20 of compute. Eligible new accounts can try $0.25 of compute first, no card. Trial terms

FAQ

Is Roo Code still maintained?

No. The Roo Code extension was shut down on May 15, 2026, its GitHub repo is archived (final release 3.54.0), and roocode.com now redirects to Roomote, a separate product from the same team. The README points users to ZooCode, a community-maintained fork, or to Cline. An installed copy may keep working, but it gets no fixes or support for new models.

What's the cheapest way to replace Roo Code as a daily driver?

Move to Cline or ZooCode, then pick the backend by the models you need. Open-weight models: a GLM coding plan or a similar subscription quota is hard to beat on price. Frontier models all day with no windows: a flat-rate OpenAI-compatible endpoint is the fixed-cost option.

Will switching from Roo Code to Cline change my bill?

Not by itself: same fork family, same cost dynamics. Both pass raw API pricing through, so the bill depends on your models, context habits, and backend, not on which of the two you run.

Related errors