Preserve the history before migrating
Roo Code is no longer a current service. Before uninstalling it or clearing editor storage, run npx whoburnedmore --local. The CLI can still read supported historical Roo task records and build a self-contained local dashboard without automatic sign-in or submission. Decline the optional interactive publish offer to keep the run local. Save that HTML snapshot, then migrate settings to Zoo Code.
Status timeline
What changed on May 15, 2026
Roo wrote task history locally
Completed provider requests could include input, output, cache, and recorded cost fields inside each task's UI-message file.
Roo products shut down
Roo Code's extension repository was archived and the former team's Cloud and Router services were shut down. The repository is now read-only.
Zoo continues the codebase
Zoo Code is a community continuation with its own maintained project and migration flow. It should not be treated as the same telemetry source.
Local archive workflow
Capture historical Roo usage in four steps
- 01
Leave the legacy storage in place
Do not clear VS Code-family global storage until after the snapshot. Uninstalling an extension and deleting its data are separate actions, but editor cleanup tools can remove the records the reader needs.
- 02
Generate the offline dashboard
Run the local command below. It reads supported logs on the machine, opens a standalone HTML report, and prints the exact file URL in the terminal.
- 03
Confirm Roo appears as a tool
Check the dashboard's by-tool breakdown for Roo. A zero or missing row means no completed supported rows were found; it is not proof that the Roo account never had usage.
- 04
Copy the dated snapshot
The standard output is ~/.config/whoburnedmore/dashboard.html unless WHOBURNEDMORE_CONFIG_DIR is set. Copy it to an archive location before another local run replaces it.
npx whoburnedmore --local
# Then copy the generated dashboard.html to your own dated archive folder.The dashboard combines every supported local source found on the machine, so use its tool breakdown to identify Roo rather than treating the all-tools total as a Roo-only total. For a broader machine-readable workflow, see the JSON and CSV export guide.
Verified implementation boundary
Exactly what the legacy reader scans
On macOS, the reader checks the global-storage roots for VS Code, VS Code Insiders, Cursor, VSCodium, and Windsurf. Equivalent editor roots are checked on Windows and Linux. Under each root, the Roo path has this verified shape:
…/User/globalStorage/rooveterinaryinc.roo-cline/tasks/<taskId>/ui_messages.jsonRoo to Zoo
Migrate configuration without merging the measurements
Roo: close the archive
Generate and retain the local usage dashboard. Separately, open Roo settings and use its Export action while the legacy extension is still available to you.
Zoo: open a new baseline
Install Zoo from its maintained source, choose Import Settings, and select the Roo settings export. Then verify providers, modes, MCP servers, and permissions before real work. Do not assume the old usage history moved with the settings.
Which source answers which post-shutdown question?
- Historical token totals
- The local Roo task files are the evidence. Preserve them and use the legacy reader before clearing editor storage.
- Historical cost
- Prefer a stored per-request cost when present. Otherwise treat any pricing-table calculation as an API-equivalent estimate with gaps.
- Old Roo Cloud or Router balance
- The archived Roo notice and former billing support channel are the authority. Local token logs cannot reconstruct an account balance or refund.
- Current Zoo usage or billing
- Use Zoo and the active model provider's own surfaces. The Roo reader has no verified automatic coverage for Zoo Code.
Privacy, cost, and completeness caveats
npx whoburnedmore --local creates a self-contained dashboard without automatic submission. In an interactive terminal, decline the optional publish offer to keep the run local. The unflagged npx whoburnedmore flow is different—it signs in and submits daily aggregate usage totals to the user's profile. Neither mode sends prompts, code, or file names.
The reader is best-effort. It only counts completed request rows in supported files that still exist and are readable. Missing history can result from deleted editor storage, older formats, interrupted requests, or work performed through a surface that did not use this legacy layout.
Cost is not entitlement. A local token-cost figure does not show a subscription allowance, provider credit balance, invoice adjustment, Roo refund, or Zoo billing total. Reconcile money decisions against the provider's authoritative billing record.
Roo Code usage and migration FAQ
Can I still calculate Roo Code usage after shutdown?
Yes, when the supported legacy task files are still present. The native reader aggregates completed rows from the old Roo extension storage. It cannot recover deleted cloud data or rebuild local files that no longer exist.
Does importing Roo settings into Zoo import chat or usage history?
Do not assume so. The documented migration imports a Roo settings export into Zoo. Preserve usage separately, and verify any history behavior in the current Zoo documentation before deleting the original storage.
Will whoburnedmore count new Zoo Code sessions as Roo?
There is no verified automatic Zoo reader in the current implementation. The legacy reader targets only rooveterinaryinc.roo-cline, so reporting new Zoo sessions as covered would be inaccurate.
Is the dashboard cost what I paid?
Not necessarily. It may use a positive cost Roo recorded for a request; otherwise an API-equivalent pricing estimate may be available. Provider invoices, subscriptions, credits, taxes, and refunds remain separate.
Archive format
self-contained HTML
Local command
no network submission
Cost meaning
estimate, not invoice
Sources
- Roo Code repository archive notice
The archived official repository documents the legacy product and its May 2026 shutdown status.
- whoburnedmore CLI source
Canonical CLI commands and export behavior; use --local when no aggregate upload is wanted.
- Zoo Code repository
The community continuation describes its relationship to Roo Code and links to the maintained project.
- Roo to Zoo migration guide
Zoo Code's migration instructions cover exporting Roo settings and importing that file into Zoo Code, including the API-key handling warning.
Product and implementation status reviewed August 28, 2026. Archived and successor projects can change their documentation, so recheck the linked sources before migrating sensitive configuration.