Problem: Claude Code itself breaks during OMC install (OOM Killed / Homebrew conflict / scripts disabled) —— Trove problem library

What you will run into

While installing OMC, Claude Code itself has problems: OOM Killed, Homebrew/npm conflicts, Windows "running scripts is disabled". You'd think OMC installed wrong — it's not an OMC problem; these are common pitfalls of the Claude Code install environment.

Why this happens

The key mental model here is problem layering: OMC is a wrapper on top of Claude Code, and flows like /omc-setup ultimately call the Claude Code host and the system package manager — the layer where the error appears is the layer where the root cause lives.

The three errors map to three different layers: OOM Killed is the resource layer (out of memory; any process can be killed, unrelated to OMC); the Homebrew conflict is the package-manager layer (both brew and npm write bin links and global package dirs;

double-writing the same location overwrites each other); "running scripts is disabled" is the policy layer (PowerShell by default only runs signed scripts and refuses any unsigned .ps1).

The judgement method is fixed: first see which stage the error occurs in (OMC's own command vs the Claude Code host vs a system tool), then find the root cause by layer.

That's also why WSL measured no such problem — Linux has no PowerShell execution-policy layer.

Step by step

1. OOM: more memory / close extra processes — Required

/omc-setup depends on Claude Code itself; if memory is low, close extra processes or add memory and retry.

2. Homebrew conflict: use the npm path consistently — Required

Install the CLI via npm consistently (this marketplace's path B), avoiding brew/npm double-write:

npm i -g oh-my-claude-sisyphus

3. PowerShell: relax the execution policy — Required

Set-ExecutionPolicy -Scope CurrentUser RemoteSigned

(As needed) then run the scripts.

How to confirm it works

Install and command surface work (measured shape):

npm i -g oh-my-claude-sisyphus → install complete
omc --version → 5.0.0 (WSL npm CLI form measured without this problem)

Other environments

Symptom

During OMC install, Claude Code itself fails: OOM Killed, Homebrew vs npm conflicts, or Windows says "running scripts is disabled".

Cause

Not OMC's own problem — these are common Claude Code install-environment pitfalls (insufficient memory, package manager conflicts, PowerShell default execution policy).

Solution

1. OOM: increase memory / close extra processes then retry (/omc-setup depends on the Claude Code host).
2. Homebrew conflict: install the CLI uniformly via npm (this marketplace's path B) to avoid brew+npm double writes.
3. PowerShell: Set-ExecutionPolicy -Scope CurrentUser RemoteSigned (as needed) before running scripts.