[BUG] Claude in Chrome: Single prompt consuming ~61% of session usage limit

Resolved 💬 0 comments Opened Jun 6, 2026 by ysolomon-plat Closed Jul 2, 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?

## Bug Report

Tool: Claude in Chrome (browser extension)

Summary: A single prompt caused approximately 61% of the session usage limit to be consumed within ~1 minute.

Expected: Minimal token usage for a page inspection prompt
Actual: ~61% of session limit consumed in under 1 minute

Environment:

  • Browser: Chrome
  • Extension: Claude in Chrome
  • Date: 2026-06-06

What Should Happen?

Hypothesis: The extension may be injecting the full rendered DOM of the page as context with every prompt. On a complex Angular app, this could be an extremely large payload (thousands of DOM nodes) being sent as hidden context, inflating token usage dramatically.

Error Messages/Logs

Steps to Reproduce

Steps to Reproduce:

  1. Open Claude in Chrome on a complex Angular SPA (tested on copart.co.uk lot listing page)
  2. Send a single prompt asking for DOM inspection / Network tab analysis of the page
  3. Observe session usage spike to ~61% from one response

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

claude code in chrome

Platform

Other

Operating System

macOS

Terminal/Shell

Other

Additional Information

_No response_

View original on GitHub ↗