Skip to content

opencode run --attach exits with no output (stdout/stderr empty) since v1.14.41 #27023

@Kovisun

Description

@Kovisun

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

  1. Start opencode server: opencode serve --port 4096
  2. Run with attach: opencode run --attach http://localhost:4096 "写一首诗"
  3. 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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions