Add Zoo Code usage tracking

[mike1858]

Why

Zoo Code is a community-maintained fork of Roo Code, but it uses the distinct VS Code extension storage ID zoocodeorganization.zoo-code. Splitrail's Roo Code analyzer only discovers rooveterinaryinc.roo-cline, so new Zoo Code sessions are not found even though their task files retain the Roo-compatible format.

Zoo Code should be tracked independently so usage is discovered from its own storage namespace and attributed accurately in statistics, uploads, and MCP queries.

What changed

• Add a dedicated ZooCodeAnalyzer that discovers and watches Zoo Code task directories across supported VS Code variants and platforms.
• Add Application::ZooCode and register the analyzer alongside Roo Code.
• Reuse the Roo-compatible task parser while parameterizing application attribution, avoiding duplicate parsing logic.
• Add focused coverage for the Zoo extension ID, analyzer discovery, empty statistics, model and session extraction, token/cache accounting, cost, and Zoo Code attribution.

Validation

• cargo test --quiet zoo_code — 6 passed
• cargo build --quiet
• cargo test --quiet — 389 passed
• cargo clippy --quiet -- -D warnings
• cargo doc --quiet
• cargo fmt --all --quiet -- --check

Documentation

The supported-tools README update is intentionally handled separately by a pending contributor change.

[coderabbitai]

Warning

Review limit reached

@mike1858, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 42 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: ff8748ee-9204-4872-8d54-dcaab5419a0d

📥 Commits

Reviewing files that changed from the base of the PR and between 9c8b14a and 4c8760f.

📒 Files selected for processing (7)

• src/analyzers/mod.rs
• src/analyzers/roo_code.rs
• src/analyzers/tests/mod.rs
• src/analyzers/tests/zoo_code.rs
• src/analyzers/zoo_code.rs
• src/main.rs
• src/types.rs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch add-zoo-code-support

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}