[BUG] Tool usage causes significant load on host system

Environment

• Platform (select one):
• Claude Code
• Claude CLI version: 1.0.95
• Operating System: Ubuntu Linux 24.04 LTS
• Terminal: VS Code via "Connect to Host"

Bug Description

When running Claude Code with multiple sub-agents, the agents will launch tools (ie. go build, go test, etc) but does not confirm that the tools have completed successfully and will run additional tools until the system has run out of available resources (ie. system load is high, in my case 160 for a 6-core 64GB node).

Steps to Reproduce

1. Create a series of agents that writes Go code, lints Go code, builds Go code, and then writes Go tests and runs the tests.
2. Give the agents a task to develop a minimally complex Go application, being sure that the agents run the intended tools, specifically performing a handoff of one agent to the next (ie. develop code, lint code, build code, test code, etc).
3. Observe the load on the system to see the tools in use and what the load on the system is and if the tools are completing as expected or remain running

Expected Behavior

1. Claude Code should be intelligent enough to understand what available resources exist and make decisions if it is safe to run tools if the system is out of resources or running dangerously low. If there's not enough resources, then Claude Code should not run.
2. It should also be able to easily understand if the tools that it has called have completed successfully with an expected exit code or if they continue to run. Claude Code should not continue unless it's verified that the tools it has called have ended.
3. All tools should be executed with a reasonable timeout to ensure that processes and memory are freed up.

Actual Behavior

Instead of understanding system resources and constraints, Claude assumed that a tool ran successfully and started another tool before the previous one had completed. This compounded until the system was dangerously low on resources and almost crashed. The user had to manually kill the go processes to get the system back into a normal operating state.

Additional Context

The only thing running on this system was Claude Code and the Go application it was building/testing
<img width="1826" height="848" alt="Image" src="https://github.com/user-attachments/assets/1887c7a0-7641-4cd4-b9a4-86ab115cd2fc" />