Review `opencode` integration — original project archived (succeeded by Crush)

[mnriem]

The `opencode` integration (`src/specify_cli/integrations/opencode/`, `install_url: https://opencode.ai\`) warrants review.

• The original `opencode-ai/opencode` repo was archived, with the original author continuing the work as Crush (`charmbracelet/crush`).
• Separately, the `opencode.ai` domain/brand is now continued by a different team (`anomalyco/opencode`) and remains active.

Suggested action: confirm which project the integration targets and whether it should be repointed (e.g., to Crush) or kept as-is against the current `opencode.ai` project.

[github-actions]

Bug assessment — opencode-project-archived: Likely valid, needs reproduction · severity medium

---

Bug Assessment: opencode Integration — Original Project Archived

• Slug: opencode-project-archived
• Created: 2026-06-25
• Source: issue Review opencode integration — original project archived (succeeded by Crush) #3170
• Verdict: likely valid, needs reproduction
• Severity: medium

Report (summarized)

Reported by @mnriem. The opencode integration (src/specify_cli/integrations/opencode/) targets install_url: "(opencode.ai/redacted)". The original upstream project (opencode-ai/opencode) was archived on GitHub; its original author continued the work under a different name — Crush (charmbracelet/crush). Meanwhile, the opencode.ai domain and brand have been picked up by a separate team (anomalyco/opencode) that is actively maintained. The report asks whether the integration should be repointed to Crush or validated as correctly targeting the current anomalyco/opencode project.

Symptom

The integration's metadata (install_url and implicitly the CLI target) may now resolve to anomalyco/opencode — a different project from the one the integration was originally written for — potentially yielding a mismatched CLI interface. Users pointed to (opencode.ai/redacted) may install a CLI whose flags diverge from what the integration's custom build_exec_args method emits, causing silent failures or errors during exec-mode invocations.

Reproduction

1. Review opencode-ai/opencode — confirm archived status.
2. Review charmbracelet/crush — confirm this is the original author's continuation; note its CLI binary name and subcommand interface.
3. Review anomalyco/opencode — confirm it is actively distributed via (opencode.ai/redacted); inspect its CLI flags (particularly run --command, --format, -m).
4. Install the current opencode binary from (opencode.ai/redacted) and run: opencode run --command speckit.specify -m <model> --format json <args>.
5. Compare against what the integration's build_exec_args emits — verify the command succeeds or fails.

[NEEDS CLARIFICATION: Does the anomalyco/opencode binary expose a run subcommand and accept --command, --format json, and -m flags with the same semantics as the original opencode-ai/opencode did?]

Suspected Code Paths

• src/specify_cli/integrations/opencode/__init__.py:12 — install_url: "(opencode.ai/redacted)" points to what is now the anomalyco/opencode project; the correctness of this value is the crux of the issue.
• src/specify_cli/integrations/opencode/__init__.py:24-51 — build_exec_args() constructs opencode run [--command <name>] [-m <model>] [--format json] <message>. These flags must match the CLI contract of whichever project the integration actually targets.
• src/specify_cli/integrations/base.py:1252 — build_exec_args in the base falls back to -p <prompt> when not overridden; the opencode override replaces this entirely with the run subcommand pattern, meaning any CLI deviation would produce a hard error.
• src/specify_cli/integrations/base.py:303 — shutil.which(self.key) resolves the "opencode" binary at runtime; this works as long as the installed binary is still named opencode.

Root Cause Hypothesis

The integration was authored against the opencode-ai/opencode project's CLI interface and deployed with install_url: "(opencode.ai/redacted)". After the original repo was archived, the opencode.ai brand passed to anomalyco/opencode. If that project preserves a compatible CLI interface (same run subcommand, same flag names), no functional breakage exists — only a documentation and provenance concern. If the interface diverged, any exec-mode invocation via specify run will fail. The metadata concern (pointing users to a different-team project without a documented compatibility audit) is valid regardless of CLI compatibility. Confidence: medium — functional impact depends on anomalyco/opencode's CLI, which has not been verified.

Proposed Remediation

Preferred: Audit the anomalyco/opencode CLI to confirm whether run --command, --format, and -m flags remain compatible with build_exec_args. If compatible, keep the key and install_url as-is, but add a short code comment in opencode/__init__.py documenting the provenance shift and the audit date so future maintainers have the context. If not compatible, the integration must either be updated to match the new CLI interface, or replaced/deprecated.

Alternatives:

• Repoint to Crush: If the intent was always to follow the original author, change key and config to match charmbracelet/crush (likely a different binary name — confirm CLI name first). This would require a migration path for existing users.
• Deprecate the integration: If neither anomalyco/opencode nor Crush provides a stable, compatible interface, the integration can be marked deprecated and eventually removed, mirroring how other integrations targeting abandoned upstreams are handled.

Files likely to change:

• src/specify_cli/integrations/opencode/__init__.py — install_url, and potentially key, config["name"], or build_exec_args flags.
• docs/reference/integrations.md — The table row linking to `(opencode.ai/redacted)
• tests/integrations/test_integration_opencode.py — If CLI flags change, exec-arg tests need updating.

Tests to add or update:

• Add a test asserting the install_url value matches the project actually targeted (analogous to the test_install_url_is_set pattern in other integration test files).
• If flags change: update test_build_exec_args_uses_run_command_dispatch and test_build_exec_args_maps_model_and_json_flags to reflect the new interface.

Risks & Considerations

• Silent exec failures: If the CLI interface has already diverged and users are running specify run with the opencode integration, commands may fail or be mis-dispatched without obvious error messages.
• Key rename risk: Changing key to match Crush's binary name would be a breaking change for any project that has previously run specify integration use opencode; a migration/alias step would be needed.
• Brand ambiguity: The anomalyco/opencode project is a different org; if it goes inactive or is itself renamed, the integration would face this same situation again.
• No data risk: No user data is at risk; the concern is CLI invocation correctness and documentation accuracy.

Open Questions

• [NEEDS CLARIFICATION: What is the CLI binary name distributed by charmbracelet/crush? Is it crush or does it still install as opencode?]
• [NEEDS CLARIFICATION: Does anomalyco/opencode expose the same run --command --format -m interface that the current build_exec_args relies on?]
• [NEEDS CLARIFICATION: Was the original integration written with opencode-ai/opencode specifically in mind, or was it always targeting opencode.ai as a brand?]

---

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

Generated by 🐛 Assess Bug from Labeled Issue for issue #3170 · 157.1 AIC · ⌖ 25.2 AIC · ⊞ 33.2K · ◷