Repository navigation
[BUG] Conversations that have errors during chat title generation (i.e., what the chat is about) don't appear in --resume list #11232
Description
Preflight Checklist
- I have searched existing issues and this hasn't been reported yet
- This is a single bug report (please file separate reports for different bugs)
- I am using the latest version of Claude Code
What's Wrong?
When a conversation file (.jsonl) contains an entry indicating that it failed to generate a chat title (e.g., "Refactor plan for foo.py"), it doesn't appear in the conversation history when running claude --resume.
What Should Happen?
Conversations should still appear in the --resume history despite failing to generate a chat title. Maybe fall back to the most recent valid chat title if this happens?
Error Messages/Logs
Steps to Reproduce
- Have a conversation that generates an error during chat title creation or updating (e.g., "API error with thinking strategy")
- The conversation file ends up with a summary error:
{"type":"summary","summary":"API Error: 400 {\"type\":\"error\",\"error\":{\"type\":\"invalid_request_error\",\"message\":\"`clear_thinking_20251015` strategy requires `thinking` to be enabled\"},\"request_id\":\"req_...\"}","leafUuid":"..."}- Quit and run
claude --resume - The conversation doesn't appear in the list
Claude Model
Sonnet (default)
Is this a regression?
I don't know
Last Working Version
No response
Claude Code Version
2.0.36 (Claude Code)
Platform
Anthropic API
Operating System
Ubuntu/Debian Linux
Terminal/Shell
Other
Additional Information
Workarounds:
- Resume directly by session ID:
claude --resume <session-id>(the uuid in the offending.jsonlfile name) - Manually edit the
.jsonlfile to remove the error summary line
Reacted by Lorenzo Nava, Rick Panchal and Mike Key
Activity
LorenzoNava99 commentedon Nov 12, 2025
@asfires It happened to me numerous times on custom /slash-commands, but by adding ultrathink to the /slash-command the error disappears.
RbkGh commentedon Nov 21, 2025
the problem is that
ultrathinkkeyword works but it burns extra tokens specifically 32K extra so why can't think just come back to normal? is this a ploy to just get users to burn more tokens?1337hero commentedon Nov 22, 2025
Numerous times here
github-actions commentedon Dec 22, 2025
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
github-actions commentedon Jan 21, 2026
This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.
github-actions commentedon Jan 28, 2026
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.