Bug Description
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.
Environment
- OpenCode 1.14.48
- Docker, Linux x86_64
Bug Description
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
opencode serve --port 4096opencode run --attach http://localhost:4096 "写一首诗"Workaround
Running without --attach prints response to stdout correctly:
But this bypasses the server, so connected WebSocket clients do not get real-time updates.
Environment