Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[BUG] OpenCode 2.0.21 incompatible with bmad-loop 0.13.0 opencode-http adapter

Cerrado
  • ¿Algo no está bien?
#847 2 comentarios 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
55/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
cli

Línea de trabajo

Start at the shipped opencode-http adapter and its health-check entry point, then inspect how it invokes opencode serve and validates /global/health. Compare that expectation with the OpenCode 2.0.21 behavior. Done means OpenCode 2.x works through the adapter or unsupported versions produce a clear error instead of retrying three times.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug
Description

bmad-loop cannot start OpenCode sessions using the shipped opencode-http adapter. The OpenCode server starts successfully, but the adapter never considers it healthy and aborts after three retries.

Environment:

bmad-loop: 0.13.0
OpenCode: 2.0.21
Adapter: opencode-http
OS: Arch Linux

Steps to reproduce

Run a job using opencode-http with opencode2 installed

Expected behavior

bmad-loop should either:

Support OpenCode 2.x APIs, or
Detect unsupported OpenCode versions and provide a clear error message.

Actual behavior

bmad-loop fails with:
bmad_loop.adapters.opencode_htp.OpencodeServerError:
could not start opencode serve after 3 attempts
(server did not become healthy in time)

OpenCode Server starts successfully on each attempt:
server listening on http://127.0.0.1:43389
server listening on http://127.0.0.1:33445
server listening on http://127.0.0.1:50769

Screenshots

No response

Which area is this for?

CLI adapters & profiles

bmad-loop Version

0.13.0

Which coding CLI are you using?

Other

Operating System

Linux

Relevant log output
Visiting /global/health on the running OpenCode 2.0.21 server does not return the JSON response expected by the adapter.
Diagnostic dump (bmad-loop diagnose)

bmad-loop diagnostic dump (sanitized)

Identifiers are pseudonymized; code, prompts, paths and free text are redacted. Safe to share.

Environment

  • bmad-loop version: 0.13.0
  • python: 3.13.13
  • os: Linux 7.2.4-arch1-2
  • sys.platform: linux
  • win32 on WSL distro path: no
  • multiplexer: TmuxMultiplexer
  • tmux: tmux 3.7c
  • git: git version 2.55.0
  • schema / generated: v4 @ 2026-10-01T05:51:58Z

Run 20261001-004938-d0f5 (story)

  • project: project-a99323e11530
  • code root differs from project: no
  • started: 2026-10-01
  • state: finished=False stopped=False paused=False
  • epic / sweep_cycle: 3 / 1
  • tasks: 1
  • phase histogram: dev-running=1
  • token totals: cache_creation_tokens=0, cache_read_tokens=0, input_tokens=0, output_tokens=0, total=0, weighted=0
  • sessions by status: —
  • sessions by role: —
Tasks
alias epic phase att gen esc-upto rev committed spec dw sessions weighted raw
s3-c5d7108c1737 3 dev-running 1 0 0 0 False False 0 0 0 0
Journal
  • entries: 8
  • duration (s): 90.853
  • escalations / defers / plugin-errors: 0 / 0 / 0
  • kind histogram: run-crash=1, run-start=1, session-end=1, session-start=1, story-start=1, target-branch=1, worktree-opened=1, worktree-seed-skipped=1

Per-task event counts:

  • s3-c5d7108c1737: story-start=1, worktree-opened=1, worktree-seed-skipped=1
  • story-c835c875bc40: run-crash=1, session-end=1, session-start=1
Run-dir files (counts only)
  • logs: 3 files, 129 bytes, 3 lines
  • tasks: 1 files, 945 bytes
  • worktrees: 2691 files, 33221449 bytes
Confirm
  • I've searched for existing issues
  • If I attached a diagnose dump, I reviewed it and confirmed it contains no PII, secrets, or project-specific information
  • I'm using the latest version
Lenguaje dominante
Python
Estrellas
165
Forks
69
Merge medio
1 d 3 h
PR fusionados (30 d)
75

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de bmad-code-org/bmad-loop

Todos los issues de bmad-code-org/bmad-loop

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.