[BUG] Code tab forces full re-sign-in after a brief network switch (hotspot to Wi-Fi), killing the active session

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 Desktop (macOS) Code tab drops my active session and kicks me back to the Sign In screen whenever my Mac switches networks, for example from my iPhone personal hotspot to a saved, preferred Wi-Fi network at a coworking space. The switch takes a few seconds. The chat tab and claude.ai in the browser stay signed in fine.

This happens regularly, not once. The most recent time it fired right after I had typed a long message with several screenshots attached, before I could send it.

What Should Happen?

The App or Claude should not Disconnect a user just because they switched from a personal hotspot to a preferred and saved WiFi network. Whether its a public network or private one shouldn't really make a difference as the Network is just connecting the user to the internet so Claude can Function. It's Crap when you hammer out a big bug fix in your own GitHub or app and then when you press submit it forces you to re-sign-in and everything you just did is Gone. Unbelievable. Should be Simple for Claude to reconnect when the WiFi or HotSpot changes.

Error Messages/Logs

Steps to Reproduce

1.) Open Claude Desktop, go to the Code tab, start a session.
2.) Have the Mac connected to an iPhone personal hotspot.
3.) Move into range of a known, auto-join Wi-Fi network so the Mac switches over.
4.) Within seconds the Code session ends and the app shows the Sign In screen.

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

Claude 2.110.0 (dfb2ba) 2026-09-15T05:50:55.000Z

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

Same "sign-in has expired" behavior as #39225 and #44572. The network-switch trigger is the new detail.