claude-code - 💡(How to fix) Fix [Bug] Session names auto-overwritten, ignoring user-set names [1 participants]

[{"error":"Error: Failed to download binary from https://storage.googleapis.com/claude-code-dist-86c565f3-f756-42ad-8dfa-d59b1c096819/claude-code-releases/2.1.111/darwin-arm64/claude: Request failed with status code 429\n at qm1 (/$bunfs/root/src/entrypoints/cli.js:2749:7628)\n at async ic9 (/$bunfs/root/src/entrypoints/cli.js:2749:7718)\n at async tc9 (/$bunfs/root/src/entrypoints/cli.js:2749:14732)\n at async jm1 (/$bunfs/root/src/entrypoints/cli.js:2749:17407)\n at async ec9 (/$bunfs/root/src/entrypoints/cli.js:2751:322)\n at async <anonymous> (/$bunfs/root/src/entrypoints/cli.js:8273:14278)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-16T15:36:38.142Z"},{"error":"AxiosError: Request failed with status code 429\n at DU (/$bunfs/root/src/entrypoints/cli.js:110:1194)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:115:12744)\n at emit (node:events:92:22)\n at endReadableNT (internal:streams/readable:865:50)\n at processTicksAndRejections (native:7:39)\n at request (/$bunfs/root/src/entrypoints/cli.js:117:2467)\n at async _m1 (/$bunfs/root/src/entrypoints/cli.js:2749:5945)\n at async qm1 (/$bunfs/root/src/entrypoints/cli.js:2749:7256)\n at async ic9 (/$bunfs/root/src/entrypoints/cli.js:2749:7718)\n at async tc9 (/$bunfs/root/src/entrypoints/cli.js:2749:14732)\n at async jm1 (/$bunfs/root/src/entrypoints/cli.js:2749:17407)\n at async ec9 (/$bunfs/root/src/entrypoints/cli.js:2751:322)\n at async <anonymous> (/$bunfs/root/src/entrypoints/cli.js:8273:14278)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-16T15:36:38.143Z"},{"error":"AxiosError: Request failed with status code 402\n at DU (/$bunfs/root/src/entrypoints/cli.js:110:1194)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:115:12744)\n at emit (node:events:92:22)\n at endReadableNT (internal:streams/readable:865:50)…

TL;DR

The issue can be addressed by implementing a mechanism to track the source of the session name and only allowing auto-rename when the source is 'auto', while also providing a way for agents to set the session name programmatically.

Guidance

• Implement a tracking system for the session name source, categorizing it as 'user', 'auto', or 'agent', to determine when auto-rename should occur.
• Modify the auto-rename logic to only rename sessions when the source is 'auto', preventing overwrites of user-set names.
• Introduce a feature for agents to set the session name at startup, such as through an environment variable like CLAUDE_SESSION_NAME, to ensure deterministic and meaningful names.
• Consider adding a hook for agents to programmatically set the session name, enhancing flexibility and automation.

Example

No specific code example can be provided without more context on the existing implementation, but the suggested fix implies modifying the session name handling logic to include source tracking and conditional auto-rename.

Notes

The provided error logs seem unrelated to the session name auto-rename issue, as they pertain to download failures and request status codes. The solution should focus on modifying the session name management logic as suggested.

Recommendation

Apply the workaround by implementing the suggested tracking and auto-rename logic adjustments, as well as introducing a method for agents to set session names programmatically, to address the session name auto-rename loop issue.