[BUG] Forced re-authentication mid-session leaves the Artifact tool "switched off" for the rest of the session (same account)

What's wrong?

Partway through a long Claude Code session, I was forced to re-authenticate. I signed back in with the same account. After that, the Artifact tool stayed unusable for the rest of that session:

• Every Artifact call (publish and read) failed with:

Artifact is still listed for this conversation but is switched off in this session right now, so it cannot run.

• The session announced it had stopped watching my artifacts because "the signed-in account changed", even though it was the same account.
• Re-authenticating again made no difference. The tool stayed switched off in that session.

A new session on the same machine and account published to the same artifact URL immediately. So the account, org settings and artifact permissions were fine; only the session that went through re-auth was broken.

Context

• Several other Claude Code sessions were open at the time, but idle. None of them asked to re-authenticate. I tested one afterwards and it worked normally, so the single re-auth appears to have satisfied every session except the one it happened in.
• The artifact was already shared org-wide and had been published from this session many times before the re-auth.

What should happen?

Re-authenticating with the same account should restore the session's tools. At minimum, the session should say plainly that it must be restarted to get them back, instead of leaving the tool listed but unusable.

Impact

I lost artifact publishing mid-task, on a page my whole organization was using. The work had to be split across two sessions, and the new session lacked the original session's context.

Steps to reproduce

1. Start a Claude Code session (VS Code extension) and publish an artifact.
2. Trigger or wait for a forced re-authentication in that session; sign in with the same account.
3. Try to publish or read the artifact again from the same session → "switched off in this session".
4. Open a new session → publishing works.

Environment

• Claude Code VS Code extension 2.1.280 (darwin-arm64)
• macOS 15.5 (Apple Silicon)
• Organization account (in-app /feedback is disabled for our org, hence this issue)

Related

• #94637: same trigger (forced re-auth mid-session), but it drops a submitted prompt instead of disabling a tool
• #24317: concurrent-session OAuth refresh race, a likely cause of the forced re-auth