When internet connectivity drops mid-session (e.g., airplane mode, WiFi hiccup) and then comes back, Claude Code does not attempt to reconnect or retry. Instead, it errors out and the session effectively dies. The user has to manually start a new session.
Steps to reproduce
- Start a Claude Code session with an active task (e.g., a skill running multiple tool calls)
- Lose internet connectivity (toggle airplane mode, disconnect WiFi, etc.)
- Restore connectivity after a few seconds
Expected behavior
Claude Code detects the connection is back and retries the failed request, resuming the session where it left off.
Actual behavior
Claude Code throws an error on the failed API call and does not retry. The session is unrecoverable - you have to start fresh and lose all context.
Impact
Any long-running session (planning, multi-step code review, status checks across many repos) is fragile to even momentary network blips. Losing a deep session to a 5-second WiFi dropout is painful.
When internet connectivity drops mid-session (e.g., airplane mode, WiFi hiccup) and then comes back, Claude Code does not attempt to reconnect or retry. Instead, it errors out and the session effectively dies. The user has to manually start a new session.
Steps to reproduce
Expected behavior
Claude Code detects the connection is back and retries the failed request, resuming the session where it left off.
Actual behavior
Claude Code throws an error on the failed API call and does not retry. The session is unrecoverable - you have to start fresh and lose all context.
Impact
Any long-running session (planning, multi-step code review, status checks across many repos) is fragile to even momentary network blips. Losing a deep session to a 5-second WiFi dropout is painful.