[BUG] No response from API error when Advisor is triggered

[Samjin]

Describe the bug

Advising using Opus 4.8
No response from API · Retrying in 2m 25s · check your network

I'm using sonnet as base and this error shows up 100% of time whenever advisor is triggered. It seems to make the response much slower. I suspect it retied many times until succeed.

Expected behavior
It shouldn't always fail the connection and retry with error.

Environment

• Platform: macOS
• Model: Opus 4.8 (via advisor())
• Context size at time of error: short (few turns)

[github-actions]

Found 3 possible duplicate issues:

1. [Bug] HTTP 529 overloaded_error is rendered as "Rate limited" and hard-fails parallel sessions/subagents (no backoff, not logged to errors) #68502
2. [BUG] Contradictory rate-limit messages shown together: server rate-limit error vs usage-limit banner #61529
3. [Bug] Rate limit error causes disproportionate quota consumption #65397

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[tags2k]

Seeing this a lot today on Opus on an Enterprise account. The 3 minute delay between actions are really speeding up my workflow.

[TOMTOM2004]

I am seeing what appears to be the same or a closely related issue.

Observed behavior

Claude Code accepts the prompt and starts thinking, but the session later fails with either:

no response from API

or, in a later run:

API Error: Overloaded

This seems correlated with the advisor tool. In the same session, after disabling advisor with:

/advisor off

I was able to continue the session, which makes this look less like a basic login/authentication issue and more like an advisor-triggered API/tool-call failure.

Environment

• macOS / darwin-arm64
• Claude Code native 2.1.181
• Install method: native
• claude doctor showed the CLI itself running successfully
• Configured MCP servers reported by claude mcp remove were memory and slack
• claude doctor also showed a failed claude_design MCP/connector warning, but claude mcp remove claude_design reported no configured server with that name

Notes

• New sessions reproduced the issue.
• The prompt is accepted and thinking starts before the failure.
• Disabling advisor appears to mitigate it.
• I also saw API Error: Overloaded, so this may be related to advisor calls surfacing overload/upstream failures as a generic no response from API in the main session.

Expected behavior: if advisor fails, times out, or receives overload from upstream, Claude Code should either continue without advisor or report advisor as the failing component rather than ending the main interaction with a generic no response from API.

[suarezc]

I'd like to confirm an unusual uptick in no response from API

[a1flecke]

same. experiencing this too

[winterec]

Same here. I'm on Claude code v2.1.181. Haven't tried a downgrade yet. A new version v2.1.183 just released which I haven't tried yet, although the release notes don't mention anything about fixing this.

[juliansommer]

reproduced on v2.1.183, using opus directly no adviser

[henricook]

The fact that Anthropic's status page doesn't even mention this, and that getting the support chatbot to escalate to a human means you can't expect a response for >3 months is exceptionally frustrating. Please any Anthropic staff reading this - escalate this issue.

[tags2k]

The fact that Anthropic's status page doesn't even mention this, and that getting the support chatbot to escalate to a human means you can't expect a response for >3 months is exceptionally frustrating. Please any Anthropic staff reading this - escalate this issue.

A conspiratorial mind might think that fewer API responses and a slow support path might help Anthropic's compute demands.