[BUG] [BUG] Local session mirroring to claude.ai stops after CLI 2.1.201 (regression; 2.1.199 works)

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?

After the CLI auto-updated from 2.1.199 to 2.1.201, sessions started locally in the
desktop app (local agent mode) stop being mirrored to claude.ai. They no longer appear
on claude.ai/code or on my other PC signed into the same account. Cloud-started sessions
are unaffected — only locally-started ones fail to sync.

What Should Happen?

Locally-started sessions should mirror to claude.ai (as they did on 2.1.199), appearing
on claude.ai/code and on other devices logged into the same account within a few minutes.

Error Messages/Logs

No errors surfaced. The failure is silent — nothing in the desktop app logs
(%APPDATA%\Claude\logs\main.log) and no CLI error log. The session simply never mirrors.

Steps to Reproduce

1. On CLI 2.1.201 (Windows desktop app, local agent mode), start a new local session and send any message.
2. Open claude.ai/code in a browser (same account) — the session never appears.

A second PC on the same account also never shows it.

1. Downgrade: claude install 2.1.199, restart the app, start a new local session.
2. Within minutes it appears on claude.ai/code and on the other PC — mirroring restored.

So: local session mirroring works on 2.1.199, breaks on 2.1.201. Cloud sessions unaffected throughout.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.199

Claude Code Version

2.1.201 (Claude Code) ← 不具合が出るバージョン （現在は回避のため 2.1.199 (Claude Code) にダウングレード中）

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

• Two Windows 11 PCs on the same Max account. Until ~30 min before updating to 2.1.201,

local sessions from PC1 were visible on PC2; they stopped immediately after the update.

• Tried and did NOT help: setting "autoUploadSessions": true explicitly; signing out and back in.
• Only downgrading to 2.1.199 restored it, confirming a 2.1.201 regression.