anomalyco / anomalyco/opencode

OpenChamber spawning multiple processes causing high CPU usage

Open
#38,489 1 comment 0 reactions 1 assignee View on GitHub

@rekram1-node is already working on this.

Since Jul 23, 2026.

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

Description

Description

Version: 1.18.4
Description: Multiple openchamber serve processes running simultaneously, causing 80%+ CPU usage
Process info:
PID 95398: 87.6% CPU
PID 95436: 69.6% CPU
PID 95477: 40.0% CPU
Expected: Single OpenChamber process with minimal CPU usage
Actual: Multiple processes spawning, high CPU load (7+ load average)

Plugins

No response

OpenCode version

1.18.4

Steps to reproduce

Version: 1.18.4 Interface: OpenChamber Update Policy: bundled

Description: OpenChamber is spawning multiple serve processes simultaneously, causing excessive CPU usage (80%+ per process, load average 7+).

Process Information:
PID 95398: 87.6% CPU - node /usr/local/bin/openchamber serve --foreground --port 3010 --host 127.0.0.1
PID 95436: 69.6% CPU - node /usr/local/bin/openchamber serve --foreground --port 3010 --host 127.0.0.1
PID 95477: 40.0% CPU - node /usr/local/bin/openchamber serve --foreground --port 3010 --host 127.0.0.1
PID 55254: 0.9% CPU - node /usr/local/bin/openchamber-ingress-proxy.js
PID 375: 3.3% CPU - node /usr/local/bin/openchamber serve (earlier instance)
Expected Behavior: Single OpenChamber process with minimal CPU usage when idle

Actual Behavior: Multiple openchamber serve processes spawning, causing:

80%+ CPU usage per process
Load average 7+ on the system
System resources exhausted
Environment:

Home Assistant OS
OpenCode add-on v1.18.4
No custom plugins installed
MCP servers: homeassistant (enabled), homeassistant_native (disabled)
LSP: ha-yaml
Formatter: prettier
Additional Context:

CPU usage spikes when OpenChamber is active

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

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.