[BUG] A user can do absolutely no coding and still use up all tokens in a session. Big fail.

Resolved 💬 3 comments Opened Apr 30, 2026 by JohnUrban Closed Jun 1, 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?

  • 2.1.116 (Claude Code)
  • VSCode extension

Simply clicking on an old chat causes insane token usage.

Today a new 5 hour session started.

The first thing I did was simply click on a series of old chats to renamed them as "RETIRED" so I know I am no longer using them, and to more easily differentiate them from my current chat when looking at the list of chats.

Big mistake.

Before doing a bit of coding, I saw that my usage on the max plan was already over 40%.

That is a massive failure mode and incredibly unfair to users. There should be absolutely 0 token consumption when simply clicking on a chat. There should be absolutely 0 token consumption until the user actually makes a prompt.

What Should Happen?

Correct the behavior of Claude Code, at least in the VSCode extension, such that tokens are not consumed until a prompt is actually given. Allow users to click on a chat without consuming a massive amount of tokens. Prevent users from having a massive loss of expected productivity due to >40% of tokens being used before a prompt is even given.

Error Messages/Logs

Steps to Reproduce

  1. Open VScode
  2. Go to Claude Code extension
  3. Click on a bunch of old chats (10 or so) and rename them - be in the chat long enough for it to load the chat
  4. Notice you used >40% of your max plan session
  5. Refrain from weeping
  6. Write github issue
  7. Pray it is fixed

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.116 (Claude Code)

Platform

Other

Operating System

macOS

Terminal/Shell

VS Code integrated terminal

Additional Information

I was using the VSCode extension -- not integrated Terminal.

View original on GitHub ↗

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