[BUG] Request timeout and general unresponsiveness using CLI

Resolved 💬 5 comments Opened Dec 30, 2025 by dvmac00 Closed Feb 15, 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?

Claude Code CLI Support Request

Issue Summary

Claude Code CLI suddenly stopped working mid-session and now times out on every request, while Claude Desktop app and web interface work perfectly on the same machine and network.

Environment

  • Subscription: Max
  • Claude Code Version: 2.0.76 (also tested 1.0.51)
  • OS: macOS
  • Node.js: v20.19.4 (via NVM)
  • Terminal: iTerm2 and Terminal.app (both exhibit same issue)

Problem Description

  • Two Claude Code sessions were working normally, then suddenly stopped responding
  • Zero tokens consumed during failed requests
  • CLI shows "offline" status almost immediately after submitting any prompt
  • Request timeouts occur within seconds
  • /doctor command returns no content
  • Authentication via "login with subscription" works, but API calls fail immediately after

What Works

  • Claude Desktop app: fully functional
  • Claude web interface: fully functional
  • Direct API call via curl: instant 401 response (as expected with test key)
  • Direct API call via Node.js https module: instant 401 response (as expected)
  • Keychain access: can manually add/retrieve passwords without issue

What Doesn't Work

  • Any Claude Code CLI request times out
  • Both v2.0.76 and v1.0.51 exhibit the same behaviour

Troubleshooting Performed

  1. Logged out and back in via /logout and /login
  2. Restarted machine
  3. Completely uninstalled and reinstalled Claude Code
  4. Deleted and recreated ~/.claude directory
  5. Tested with different Node versions (20, 22)
  6. Tested with different terminals (iTerm2, Terminal.app)
  7. Verified network connectivity with curl to api.anthropic.com (works)
  8. Verified Node.js can reach API with raw https request (works)
  9. Checked for proxy environment variables (none set)
  10. Verified Keychain permissions (working correctly)
  11. Removed potentially conflicting settings files

Key Diagnostic Evidence

Debug log shows repeated timeout errors:

2025-12-30T15:26:58.728Z [ERROR] Error: Error: Request timed out.
    at WT.makeRequest (cli.js:1309:4528)

Early debug output showed:

spawn-rx Failed to find executable anywhere in path

Network test proves connectivity:

curl -v https://api.anthropic.com/v1/messages
# Returns 401 instantly - network is fine

Node.js test proves Node networking works:

node -e "const https = require('https'); ..."
# Returns 401 instantly - Node networking is fine

Conclusion

The issue is isolated to the Claude Code CLI's internal HTTP client or subscription authentication flow. All other methods of reaching the Anthropic API work correctly. This appears to be a bug in Claude Code, not a local configuration or network issue.

Request

Please investigate why the CLI's subscription auth flow is failing to make API requests despite successful login, while the same subscription works perfectly via Desktop and web interfaces.

What Should Happen?

I should be able to utilise Claude from the terminal and anything I post into the chat window should at least be processed but this is not happening

Error Messages/Logs

Steps to Reproduce

I'm not sure how somebody else might be able to reproduce this issue, although I am using macOS Version 15, but there is nothing uncommon about my set up or circumstances and as previously stated this was working perfectly fine yesterday.

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.0.76

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

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