Critical Regression: Disproportionate Session Limit Consumption for CLI Operations

Since approximately three days ago (Easter weekend), I have observed an unsustainable spike in Session Budget consumption when using claude-code.

To illustrate the severity: letting the CLI perform a simple task, such as a git commit, consumes roughly 4% of my total Max Plan session budget.

Crucial Distinction:
This is not related to Token usage or context window limits. The context usage is within expected parameters. The issue lies specifically in how the Session Limit is deducted for interactions. It appears that every internal shell execution or sub-turn is being billed as a significant portion of the session and weekly quota.

Environment & Timeline:

Tool: claude-code CLI

Plan: Anthropic Max Plan

Start of Issue: Around April 4th, 2026.

Impact: The tool is no longer viable for professional use as the session limit is depleted within minutes of basic workflow automation.

Is there a known bug in the accounting logic for claude-code sub-tasks or a recent change in how session units are calculated for CLI tool-use?

If this isn't a bug but an intended change, it makes the paid plan untenable for CLI-heavy workflows.

Technical Note on Context Management:
I manually compact/reset my context once it reaches 250k tokens to maintain response quality. Therefore, this budget drain is not caused by an oversized context window or hitting the 1M+ token limit. The 4% drop per interaction occurs even within this controlled 250k range, confirming a systematic error in session unit calculation.