[BUG] Agent Teams causes system freeze and Chrome crash due to excessive resource consumption (Linux)

Resolved 💬 2 comments Opened Feb 6, 2026 by atournayre Closed Mar 6, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Using the new Agent Teams feature (native, not experimental flag) consistently causes severe system resource exhaustion on Linux, leading to:

  1. Complete system freeze (2 out of 3 attempts) — the entire desktop becomes unresponsive, requiring a hard session restart
  2. Chrome browser crash (1 out of 3 attempts) — Chrome closes abruptly during an Agent Teams session

This happens within minutes of spawning a team with TeamCreate and launching teammates via the Task tool. The system has 32GB RAM and 32 CPU cores, so this is not an under-spec'd machine.

The issue appears to be that each teammate spawns as a separate process, and the combined resource consumption (CPU + memory) quickly exhausts system resources, causing either OOM-like behavior or extreme swap thrashing that freezes the entire system.

This is different from:

  • #23435 (JS crash on Windows, different root cause)
  • #13126 (OOM from subprocess, not from Agent Teams itself)
  • #18532 (single-agent freeze in infinite loop)

What Should Happen?

Agent Teams should:

  1. Have resource limits or back-pressure mechanisms to prevent system exhaustion
  2. Gracefully degrade instead of consuming all available system resources
  3. Not cause collateral damage to other running applications (e.g., Chrome)

Error Messages/Logs

No logs available — the system freezes completely, requiring a forced session restart. No crash dump or error message is displayed before the freeze.

Steps to Reproduce

  1. Start Claude Code on Linux (Tuxedo kernel 6.14.0)
  2. Use TeamCreate to create a team
  3. Spawn 2-3 teammates using the Task tool with team_name parameter
  4. Let agents work on tasks in parallel
  5. Within minutes, the system becomes unresponsive (freeze) or Chrome crashes

Reproduced 3/3 times with different outcomes (2 freezes, 1 Chrome crash).

Environment

  • OS: Linux (Tuxedo) — Kernel 6.14.0-123037-tuxedo
  • RAM: 32GB (30Gi total)
  • CPU: 32 cores
  • Node.js: v20.19.4
  • Claude Code: Latest version (Opus 4.6 with native Agent Teams)
  • Terminal: Standard terminal (not tmux)
  • Other apps running: Chrome browser, PhpStorm IDE

Claude Model

Opus

Is this a regression?

No, this never worked (Agent Teams is a new feature)

Last Working Version

_N/A — new feature_

Claude Code Version

Latest (with Opus 4.6 native Agent Teams support)

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Bash

Additional Information

  • The system has 32GB RAM and 32 CPU cores — this is not a resource-constrained machine
  • The freeze happens regardless of the complexity of the tasks assigned to agents
  • After force-restarting the session, system resources return to normal immediately, confirming Claude Code processes were the cause
  • Potentially related to existing memory leak issues (#11315, #22968) but amplified by multiple concurrent agent processes

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗