[Bug]: opencode integration unusable on opencode v2 — run --command removed (upstream: anomalyco/opencode#49903)
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 25/100
Línea de trabajo
Start in src/specify_cli/integrations/opencode/init.py:62-67 and inspect how the integration builds the opencode command. Check anomalyco/opencode#49903 for the upstream v2 headless command decision and reproduce the reported command failure. This issue is done when workflow command steps dispatch successfully on opencode v2 using the supported upstream path.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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: anomalyco/opencode#49903. Related: #2416, #2409, #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.
- Lenguaje dominante
- Python
- Estrellas
- 138k
- Forks
- 12.4k
- Merge medio
- 2 d 15 h
- PR fusionados (30 d)
- 141
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de github/spec-kit
-
enhancement needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
enhancement needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
enhancement needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
triage-can-wait
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
[Feature]: 给 slug 添加默认值 Abiertoenhancement needs-triage triage-can-wait
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
Todos los issues de github/spec-kit
Issues similares
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
zostera/django-bootstrap4#894 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
use-agent-os/agent-os#3276 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
zephyrproject-rtos/zephyr#119726 ·
-
area/auth bug comp/agent P3 platform/discord type/security
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
NousResearch/hermes-agent#117848 ·