← Reddit

Claude Code Subagents Not Working

Reddit · Mr-Angry-Capybara · August 5, 2026
A user reported encountering API errors exclusively with Claude Code Subagents while the main agent chat functions normally. The subagent redirects to the status page after 10 retries, though the reported issue is not reflected there.

Detailed Analysis

A Reddit user in r/ClaudeAI has surfaced a reproducible bug in Claude Code where subagents fail with API errors while the primary agent chat continues to function normally. According to the report, after roughly ten failed retries, the subagent process redirects users to Anthropic's official status page (status.claude.com), yet that page shows no corresponding outage or degraded service notice. This discrepancy—an internal error-handling mechanism pointing to an external status resource that contradicts the actual system state—is a notable inconsistency that leaves affected users without a clear diagnostic path or confirmation that Anthropic is even aware of the problem.

The technical details matter because Claude Code's subagent architecture is a relatively recent and increasingly important feature for developers using Anthropic's coding assistant. Subagents allow the primary Claude Code session to spin off specialized, isolated instances to handle discrete tasks—such as code review, testing, or research—in parallel, without polluting the main context window. This orchestration model is central to how Anthropic has positioned Claude Code as a tool for complex, multi-step engineering workflows rather than simple single-turn code generation. A failure isolated specifically to subagents, while the main chat interface remains operational, suggests the issue may lie in how subagent sessions authenticate, route requests, or manage separate API quotas or rate limits distinct from the primary conversation thread.

This report is emblematic of a broader pattern in developer tooling: as AI coding assistants add increasingly sophisticated multi-agent and orchestration capabilities, the surface area for partial failures expands correspondingly. Unlike a simple chatbot outage, which is binary and easily detected, a subagent-specific failure can be far harder to diagnose because it may not trip the same monitoring or alerting thresholds that would flag a full-service outage. This creates real friction for developers who have built workflows dependent on subagent delegation—a failure here doesn't just slow down one conversation, it can break automated pipelines, CI-integrated coding agents, or multi-step task chains that assume subagent reliability.

The gap between actual system behavior and status-page transparency is also a recurring theme in complaints about major AI providers, including Anthropic, OpenAI, and others, as their infrastructure becomes mission-critical for professional users. Status pages are often coarse-grained, reporting only major regional or full-service outages, while narrower issues affecting specific features, API endpoints, or session types can go unreported for hours or longer. As more engineering teams adopt agentic coding tools like Claude Code into production workflows, incidents like this one underscore the growing expectation that AI infrastructure providers offer more granular observability and faster acknowledgment of partial degradations—not just binary up/down status indicators—since developers increasingly treat these tools as dependable infrastructure rather than experimental add-ons.

Read original article →