VS Code Plugin version

[BODYPRINT]

Thanks for the testing and reports.
I don't know if you can help, but if I'm using Claude Code in VS Code (not the CLI version, but the plugin version) how is that measured?
Does that automatically do a resume when I return to the session because it remembers where we were when I load VS Code?
It doesn't start a new session like starting a CLI session does.
If I install 2.1.68. Would this work properly like the old Claude Code used to?

[ArkNill]

Thanks for the question. My analysis is CLI-only (Linux, Max 20) — I haven't tested the VS Code extension, so I can't give you a definitive answer, but here's what I've gathered from related issues:

Session handling in VS Code vs CLI:

• Both store sessions as .jsonl in ~/.claude/projects/, but VS Code uses a different (buggier) session discovery mechanism — #41414 reports only ~15 of 247 sessions visible in the UI
• VS Code doesn't cleanly "resume" like CLI's --resume — it has its own "Past Conversations" picker that's been unreliable (#12872, #9258)
• There are reports of the extension generating background requests without user interaction, causing unexpected token drain (#41046)

On downgrading to 2.1.68:

• For CLI, pinning to 2.1.68 was a known workaround for the cache regression (#34629). As of v2.1.91, the cache issue (B1-B2) is fixed across platforms including Windows
• For VS Code, version management works differently (extension auto-updates independently), and one report showed auto-update actually deleting CLI session files (#35367)

If you're concerned about token usage, I'd recommend checking your actual cache hit ratio through the status line or a proxy setup. The cache fix in v2.1.91 should help regardless of client.