[BUG] CLI session not writing .jsonl file — invisible to VS Code extension

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 continuing a session that was compacted/summarized (context limit reached), the new continuation session does not create a .jsonl file in ~/.claude/projects/<project>/. As a result, the session is invisible to the VS Code extension's session picker, even though other CLI sessions
from the same project directory are visible.

What Should Happen?

Continuation sessions write a .jsonl file just like initial sessions.

Desired end result is that compacted sessions created via CLI should be visible via Claude VS extension when running the same version. Currently unable to continue conversation between CLI and VS as a result.

Error Messages/Logs

Steps to Reproduce

Steps to reproduce:

1. Start a CLI session in a project directory
2. Let it run until context is compacted/summarized
3. Continue the session — a new session ID is assigned (e.g. 760ce763)
4. Check ~/.claude/projects/<project>/ — no .jsonl exists for the new session ID
5. Open VS Code with the same project folder — the session does not appear in the session list

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.109

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_