anomalyco / anomalyco/opencode

[macOS 26] Desktop sidecar exits silently with code 15 (SIGTERM) after ~2 minutes

Open
#48,948 1 comment 0 reactions 1 assignee View on GitHub

@Hona is already working on this.

Since Sep 14, 2026.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

Description

Note: This is distinct from #44475 (Windows, exit code 0). This is macOS 26 + Apple Silicon + exit code 15 (SIGTERM) — the sidecar is being killed by the OS/Electron utility process manager, not shutting down cleanly. Related to #27557, #32694, #22630.

Bug Report

Environment:

  • macOS: 26.5.2 (25F84) — Sequoia
  • Architecture: Apple Silicon (M-series)
  • OpenCode Desktop: 1.18.30
  • Electron: 42.3.3 (bundled)
  • Installation: brew install --cask opencode-desktop

Symptom:

  1. Launch OpenCode Desktop
  2. Sidecar spawns, logs "server ready" with URL
  3. ~2 minutes later: sidecar exits with code 15 (SIGTERM)
  4. UI shows "Cannot reach local server. Retrying automatically..."
  5. No stderr output, no crash report, no error in main.log between "server ready" and exit

Logs:

Workaround: CLI (opencode) works perfectly — same engine, no Electron utility process.

Related issues: #27557, #32694, #22630

Plugins

None (disabled all plugins, clean install)

OpenCode version

1.18.30 (Desktop) / 1.18.30 (CLI)

Steps to reproduce
  1. macOS 26.5.2 on Apple Silicon (M-series)
  2. brew install --cask opencode-desktop (v1.18.30)
  3. Launch OpenCode.app
  4. Wait ~2 minutes
  5. Observe sidecar exit code 15, UI shows "Cannot reach local server"
Screenshot and/or share link

No response

Operating System

macOS 26.5.2 (25F84) — Sequoia, Apple Silicon

Terminal

Not applicable (Desktop app bug). CLI works: /opt/homebrew/bin/opencode (Bun 1.4.0)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.