Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [Bug] Remote Control startup fails with stale Statsig cache [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#46925•Fetched 2026-04-12 13:29:33
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
gluecksmenschgluecksmensch
Participants
github-actions[bot]github-actions[bot]gluecksmenschgluecksmensch
Timeline (top)
labeled ×3commented ×1

Root Cause

remoteControlAtStartup: true causes "Session creation failed — see debug log" on every session start. Root cause: Statsig feature flag cache (~/.claude/statsig.*) was frozen from v2.1.22 (Jan 30) and never refreshed through updates to v2.1.104. Running /login fixed it (likely triggers Statsig re-init).

Code Example

[]
RAW_BUFFERClick to expand / collapse

Bug Description

Remote Control fails at startup with stale Statsig cache

remoteControlAtStartup: true causes "Session creation failed — see debug log" on every session start. Root cause: Statsig feature flag cache (~/.claude/statsig.*) was frozen from v2.1.22 (Jan 30) and never refreshed through updates to v2.1.104. Running /login fixed it (likely triggers Statsig re-init).

Two sub-issues:

  1. Statsig cache doesn't auto-refresh across version updates — stale gate values silently block Remote Control
  2. "See debug log" points to ~/.claude/debug/latest which is a dangling symlink — no actionable diagnostic exists

Environment Info

  • Platform: darwin
  • Terminal: iTerm.app
  • Version: 2.1.104
  • Feedback ID: 4a2fddd8-053a-4e7e-9d87-54ff2c773e10

Errors

[]

extent analysis

TL;DR

Running the /login command may temporarily resolve the Remote Control startup issue by re-initializing the Statsig cache.

Guidance

  • Verify that the Statsig cache files (~/.claude/statsig.*) are being updated after running the /login command to confirm that this resolves the issue.
  • Check the debug log location to ensure it's not a dangling symlink, and consider updating the symlink to point to the correct log file.
  • Investigate why the Statsig cache doesn't auto-refresh across version updates to prevent similar issues in the future.
  • Consider implementing a mechanism to automatically refresh the Statsig cache during version updates.

Example

No code snippet is provided as it's not clearly supported by the issue.

Notes

The provided solution is a temporary workaround, and the underlying issue with the Statsig cache not auto-refreshing across version updates still needs to be addressed.

Recommendation

Apply workaround: Running the /login command may provide a temporary fix, but a more permanent solution is needed to address the underlying cache refresh issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#ssr#installation#API versioning#request timeout

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING