You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
opencode run --attach exits with no output (stdout/stderr empty) since v1.14.41 #27023
opencode run --attach <url> exits with code 0 but produces absolutely no output on stdout or stderr. The command appears to hang for several seconds then exits silently. The response is still stored in the session database (visible in Web UI), but the CLI does not print it.
First noticed in v1.14.41. Still broken in v1.14.48.
Reproduction
Start opencode server: opencode serve --port 4096
Run with attach: opencode run --attach http://localhost:4096 "写一首诗"
Observe no output (exit code 0)
Workaround
Running without --attach prints response to stdout correctly:
opencode run --dangerously-skip-permissions "写一首诗"
But this bypasses the server, so connected WebSocket clients do not get real-time updates.
This issue might be a duplicate of (or closely related to) an existing issue. Please check:
Bug: SSE /event stream closes immediately after server.connected event #26697: SSE /event stream closes immediately after server.connected event — reports the same version regression range (broken since ~v1.14.41–v1.14.46) where the event stream terminates early. This would explain why opencode run --attach exits with no output, as it relies on that SSE stream to receive and print the response.
Activity
github-actions commentedon May 12, 2026
This issue might be a duplicate of (or closely related to) an existing issue. Please check:
/eventstream closes immediately afterserver.connectedevent — reports the same version regression range (broken since ~v1.14.41–v1.14.46) where the event stream terminates early. This would explain whyopencode run --attachexits with no output, as it relies on that SSE stream to receive and print the response.rekram1-node commentedon May 14, 2026
should be fixed:
b928a1f