Repository navigation
VS Code extension fails to start with --port parameter - outputs {} #18714
Description
Description
When opening the OpenCode VS Code extension, it runs:
opencode --port 29138
This outputs only {} and the server doesn't start properly.
Steps to Reproduce
- Run
opencode --port 29138 - Observe output:
{}
Expected Behavior
The server should start in server mode and listen on the specified port.
Actual Behavior
The TUI tries to start alongside the server, causing a conflict. From the debug logs:
ERROR service=default error=[object Object] tui bootstrap failed
{}
Workaround
Using opencode serve --port 29138 works correctly:
opencode server listening on http://127.0.0.1:29138
Environment
- OpenCode version: 1.3.0
- Platform: macOS (darwin)
- Installed via: npm
Suggestion
When --port is specified, OpenCode should automatically run in server mode (like opencode serve) rather than trying to start the TUI. Alternatively, the VS Code extension should use opencode serve --port {port} instead.
Metadata
Metadata
Assignees
Labels
No labels
Activity
tlerbao commentedon Apr 9, 2026
I'm also able to reproduce this outside the VS Code extension on OpenCode 1.4.1.
Environment
1.4.1Repro
opencodeopencode --port 4096Important detail
At first I suspected tmux, because I was launching OpenCode through a tmux alias. But after testing directly in Warp, the behavior is the same:
opencode✅ worksopencode --port 4096❌ hangsSo this appears to be a more general CLI/TUI issue when
--portis provided, not just an extension integration issue.If helpful, I can provide additional logs or test a debug build.
github-actions commentedon Jul 3, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.