claude-code - 💡(How to fix) Fix Heads-up: ultracode / dynamic workflows can chain-spawn local processes and spike host memory

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
RAW_BUFFERClick to expand / collapse

When ultracode (dynamic workflows) is on, Claude spawns subagents automatically, and those subagents can in turn spawn their own local shell/script processes (e.g. PowerShell on Windows). That nesting can multiply fast - a few agents each launching several scripts, some of which may hang and never exit, can pile up enough local processes to spike host RAM and slow down or crash the machine, including other Claude Code windows open at the same time.

It does not happen every time, but it might be worth bounding the number of concurrent local processes (not just the agent count) and making sure spawned processes get cleaned up / timed out.

Environment: Claude Code v2.1.156, Windows 11, Opus 4.8

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Heads-up: ultracode / dynamic workflows can chain-spawn local processes and spike host memory