anomalyco / anomalyco/opencode
opencode2 became stuck starting its managed background server
@rekram1-node is already working on this.
Since Aug 11, 2026.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Description
opencode2 became stuck starting its managed background server. It repeatedly spawned serve --service, but never reported the underlying error.
Plugins
No response
OpenCode version
OpenCode: 0.0.0-next-17090
Steps to reproduce
The managed service was configured to use port 49374, which was already occupied by Ollama.
Running the server directly exposed the otherwise hidden error:
Managed service port 49374 on 127.0.0.1 is already in use by another process.
Configure another port with opencode service set port <port> and start the service again.
opencode2 service start should surface the port-conflict error immediately rather than silently spawning repeated serve --service attempts.
Screenshot and/or share link
No response
Operating System
macOS, arm64
Terminal
ghoosty tmux
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.