Retire/remove `roo` (Roo Code) integration — extension shut down May 2026

[mnriem]

The `Roo Code` integration (`src/specify_cli/integrations/roo/`) targets a product that has been discontinued.

• The `RooCodeInc/Roo-Code` repository README states: "The Roo Code Extension was shut down on May 15th" (2026), directing users to Cline and a community fork.

Suggested action: deprecate and remove the `roo` integration (subpackage, registry entry, catalog entry, and `tests/integrations/test_integration_roo.py`).

[github-actions]

Bug assessment — roo-integration-defunct: Valid · severity medium

---

Bug Assessment: Roo Code integration references a discontinued product

• Slug: roo-integration-defunct
• Created: 2026-06-25
• Source: issue Retire/remove roo (Roo Code) integration — extension shut down May 2026 #3167
• Verdict: valid
• Severity: medium

Report (summarized)

The roo integration (src/specify_cli/integrations/roo/) targets Roo Code, an IDE-based coding assistant whose upstream repository (RooCodeInc/Roo-Code) states it was shut down on May 15, 2026. Users are now directed to Cline and a community fork. The reporter requests that the integration subpackage, its registry entry, catalog entry, and test file be removed.

Symptom

Running specify integration list (or specify init --integration roo) surfaces a defunct product. Users who follow the integration documentation or CLI output to install Roo Code will find the product has been shut down, leading to confusion and a broken development environment setup.

Reproduction

1. Run specify integration list — roo (Roo Code) appears as a supported integration.
2. Attempt specify init <project> --integration roo — command succeeds mechanically but installs scaffolding for a product that no longer exists.
3. Follow the (roocode.com/redacted) link from docs/reference/integrations.md` line 37 or the catalog — the product is defunct as of May 15, 2026.

Suspected Code Paths

• src/specify_cli/integrations/roo/__init__.py:1–22 — RooIntegration class; the integration definition targeting the discontinued product.
• src/specify_cli/integrations/__init__.py:78 — import of RooIntegration in _register_builtins().
• src/specify_cli/integrations/__init__.py:117 — _register(RooIntegration()) call that adds it to INTEGRATION_REGISTRY.
• integrations/catalog.json:177–183 — catalog entry "roo" advertising the integration.
• tests/integrations/test_integration_roo.py:1–11 — test class referencing the defunct integration.
• docs/reference/integrations.md:37 — table row listing Roo Code with link to `(roocode.com/redacted)
• docs/reference/integrations.md:197 — table row listing roo filesystem paths.
• docs/upgrade.md:245 — prose mention of "Roo Code" alongside other IDE agents.

Root Cause Hypothesis

The integration was built for a live product; the product was subsequently shut down (May 15, 2026) but the integration was never removed. No automated check exists to verify that advertised integrations remain active. Confidence: high — the upstream repository's own README confirms the shutdown.

Proposed Remediation

Preferred: Remove the roo integration entirely.

1. Delete src/specify_cli/integrations/roo/ (the __init__.py subpackage).
2. Remove the import (from .roo import RooIntegration) and _register(RooIntegration()) call from src/specify_cli/integrations/__init__.py.
3. Remove the "roo" entry from integrations/catalog.json.
4. Delete tests/integrations/test_integration_roo.py.
5. Remove the two roo rows from docs/reference/integrations.md (lines 37 and 197).
6. Remove the "Roo Code" name from the prose in docs/upgrade.md line 245 (or replace with an appropriate active alternative such as Cline, since that is where Roo Code directed its users).

Alternatives:

• Deprecation-only (soft removal): Mark the integration as deprecated in the catalog and emit a warning on use, but keep the code for users with existing Roo Code installs from before the shutdown. Trade-off: adds complexity for an integration that cannot be newly installed; the user population is shrinking to zero. Not recommended.

Files likely to change:

• src/specify_cli/integrations/roo/__init__.py (delete)
• src/specify_cli/integrations/__init__.py
• integrations/catalog.json
• tests/integrations/test_integration_roo.py (delete)
• docs/reference/integrations.md
• docs/upgrade.md

Tests to add or update:

• No new tests needed; deletion of test_integration_roo.py removes the existing coverage. Confirm the test suite passes without it.
• Optionally: add a registry-level test that cross-checks all registered integration keys against the catalog, to catch future stale entries earlier.

Risks & Considerations

• Existing users: Anyone who used specify init --integration roo before May 2026 has scaffolding in .roo/ that will remain functional locally even after this removal — Spec Kit does not reach into existing projects to undo prior installs. The removal only prevents new installs.
• No API breakage: roo is not referenced by any other integration or public Python API; the removal is purely additive cleanup.
• Catalog versioning: If downstream consumers (CI pipelines, preset files) pin the catalog and reference "roo", removing the entry is a breaking change for those consumers. A scan of presets/catalog.json, workflows/catalog.json, and extensions/catalog.json shows no roo references, so the blast radius appears limited to integrations/catalog.json.

Open Questions

• [NEEDS CLARIFICATION: Should the Cline integration (cline) be highlighted in the docs as the recommended migration path for former Roo Code users, given that Roo Code's own shutdown notice directed users to Cline?]

---

Posted on behalf of @mnriem by GitHub Copilot (model: claude-sonnet-4.6, autonomous)

Generated by 🐛 Assess Bug from Labeled Issue for issue #3167 · 153.4 AIC · ⌖ 13.8 AIC · ⊞ 33.2K · ◷

[circulene]

Zoo code is a successor product.
https://github.com/Zoo-Code-Org/Zoo-Code