[BUG] False "check your network" timeout error during long Opus 4.8 processing in /advisor mode
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?
When using /advisor mode with Opus 4.8 (while my primary mode is set to Sonnet 5), the CLI incorrectly throws a network retry error (Waiting for API response · will retry in 0s · check your network). This is not an actual network issue, but rather a synchronization problem caused by Opus's naturally longer processing time. The client timeout threshold appears to be too short for Opus's expected API response latency, leading to a false positive network warning.
What Should Happen?
The CLI should display a standard loading or processing indicator that accommodates the longer inference time of the Opus 4.8 model without prematurely triggering a network error.
Error Messages/Logs
The CLI displays an error state indicating a network failure: ✻ Waiting for API response · will retry in 0s · check your network.
Steps to Reproduce
- Launch Claude Code with Sonnet 5 as the primary model.
- Enter /advisor mode, utilizing Opus 4.8 as the advisor.
- Submit a prompt that requires Opus 4.8 to process a complex task.
- Observe the terminal output while waiting for the API response.
Claude Model
Sonnet (default)
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.198 (Claude Code)
Platform
Anthropic API
Operating System
Ubuntu/Debian Linux
Terminal/Shell
VS Code integrated terminal
Additional Information
<img width="618" height="268" alt="Image" src="https://github.com/user-attachments/assets/d092e1b4-393e-43f5-96ad-acb99b9babf1" />
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗