[BUG] Conversations that have errors during chat title generation (i.e., what the chat is about) don't appear in --resume list

Resolved 💬 6 comments Opened Nov 8, 2025 by asfires Closed Jan 21, 2026

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?

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

  1. Have a conversation that generates an error during chat title creation or updating (e.g., "API error with thinking strategy")
  2. 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":"..."}
  1. Quit and run claude --resume
  2. 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:

  1. Resume directly by session ID: claude --resume <session-id> (the uuid in the offending .jsonl file name)
  2. Manually edit the .jsonl file to remove the error summary line

View original on GitHub ↗

This issue has 6 comments on GitHub. Read the full discussion on GitHub ↗