Repository navigation
[Bug]: opencode integration unusable on opencode v2 — run --command removed (upstream: anomalyco/opencode#49903) #4639
Description
Bug Description
The opencode integration dispatches commands as opencode run --command <name>, but opencode v2 removed --command. Every workflow command step fails immediately with Unrecognized flag: --command (exit 1).
Tracking report — no spec-kit-side workaround is proposed. The integration can only be fixed once upstream decides the v2 headless command path. Upstream: anomalyco/opencode#49903.
Steps to Reproduce
- Install opencode v2 (
opencode --version→ 2.0.8). - Run a workflow command step with
command: speckit.specify,integration: opencode. - Spec Kit emits
opencode run --command speckit.specify ….
Expected Behavior
The command is dispatched and runs.
Actual Behavior
opencode run --command speckit.specify … → ERROR: Unrecognized flag: --command in command opencode run, exit 1 (failed in ~54 ms in run cockpit-d012782e9339).
Specify CLI Version
1.0.9.dev0
AI Agent
opencode
Operating System
Ubuntu 24.04.5 LTS (Linux 6.17.0-1032-oem, x86_64)
Python Version
3.12.3
Error Logs
$ opencode run --command speckit.specify "build a login page"
ERROR
Unrecognized flag: --command in command opencode run
exit=1
Additional Context
src/specify_cli/integrations/opencode/__init__.py:62-67appends--command.- The slash prompt is synthesized internally, so users cannot avoid it.
- Upstream report: run: --command removed in v2 and slash commands are not expanded — no CLI path for headless command invocation anomalyco/opencode#49903. Related: [Bug]: Systematic build_exec_args() audit — CLI dispatch flags unverified for 11+ integrations #2416, [Bug]: opencode integration dispatch fails — uses unsupported
-pflag instead ofrunsubcommand #2409, [Bug]: Amp dispatch sends-p/--model/--output-format— none of these exist in the Amp CLI #4580. - Requested handling: tracking issue (e.g.
triage-can-wait) until upstream decides, to prevent duplicate reports.
AI Disclosure
Drafted with an AI assistant (OpenCode agent, model: DeepSeek V4.1 Flash); commands and logs reproduced on the affected machine and reviewed by the reporter before posting.
Activity
github-actions commentedon Sep 22, 2026
Bug assessment — opencode-v2-command: Likely valid, needs reproduction · severity medium
Bug Assessment: opencode integration unusable on opencode v2
Report (summarized)
The reporter states that Specify CLI 1.0.9.dev0 emits
opencode run --command <name> ...for slash-prefixed workflow commands. With opencode 2.0.8,runrejects--command, so the workflow exits with status 1 before execution. The report includes Ubuntu 24.04.5, Linux x86_64, Python 3.12.3, and a failedspeckit.specifyinvocation. The reporter links the upstream discussion at anomalyco/opencode#49903 and references related Spec Kit issues #2416, #2409, and #4580. No additional issue comments were present.Symptom
For opencode v2 installations, slash-prefixed Spec Kit workflow dispatch is expected to run the selected command but instead fails immediately because the integration adds the removed
--commandoption. Plain prompts without a slash command are not implicated by the report.Reproduction
2.0.8.command: speckit.specifyandintegration: opencode.build a login page.opencode run --command speckit.specify ...and theUnrecognized flag: --commanderror.The exact supported replacement invocation for opencode v2 is [NEEDS CLARIFICATION: upstream has not established the v2 headless command path in this report]. This assessment does not independently reproduce against an installed opencode v2 binary.
Suspected Code Paths
src/specify_cli/integrations/opencode/__init__.py:45-78—OpencodeIntegration.build_exec_args()constructsopencode run; when the prompt starts with/, it appends--commandand the command name before model, JSON, and message arguments.tests/integrations/test_integration_opencode.py:22-60— integration tests explicitly lock in the legacyrun --commandargv shape, including model and JSON variants.tests/integrations/test_extra_args.py:330-370— extra-argument tests also assume the prompt-derived--commandflag and its ordering.src/specify_cli/workflows/step/command/__init__.py:239— workflow command execution delegates to the integration'sbuild_exec_args(), making the integration argv the dispatch boundary for command steps.Root Cause Hypothesis
The opencode integration encodes the pre-v2 CLI contract unconditionally: slash-prefixed prompts are translated to
run --command <name>. Opencode v2 removed that option, so every slash-command workflow using the v2 executable is rejected by the CLI before Spec Kit receives any useful output. Confidence: high for the reported v2 failure; low for the correct replacement until the upstream interface is confirmed.Proposed Remediation
Preferred: Confirm the supported opencode v2 headless command-dispatch syntax upstream, then update
OpencodeIntegration.build_exec_args()to emit that syntax for v2 while preserving the legacy form for supported pre-v2 releases, or make the supported-version policy explicit if compatibility cannot be maintained. Keep model, JSON-output, extra-argument ordering, and plain-prompt behavior aligned with the selected CLI path. Update the integration and extra-args tests to assert each supported version/path and document the compatibility boundary.Alternatives:
Files likely to change:
src/specify_cli/integrations/opencode/__init__.pytests/integrations/test_integration_opencode.pytests/integrations/test_extra_args.pyTests to add or update:
Risks & Considerations
Open Questions
run --command?]mnriem commentedon Sep 23, 2026
@markuswondrak Is there anything that can be done here? Is it blocked on upstream?
markuswondrak commentedon Sep 23, 2026
No, not really. v2 removed the
run --commandparameter and does not resolve slash commands either when inputted as plain text (like/speckit.implement).Only thing left would be to warn users who use Opencode v2 that workflows will not work for them with this integration.