[FEATURE] Allow to disable token count warning

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Claude has been refusing to work multiple times on a large feature due to "warnings" that it constantly faced:

The token count appears in <system_warning> blocks after each tool result. See the pattern:

  <system_warning>Token usage: 140882/200000; 59118 remaining</system_warning>

  These warnings show up automatically from the system after I use tools - they're not in your initial prompt, but injected into the conversation flow so I can track my budget and adjust accordingly
  (like summarizing instead of full reads when running low).

This severely disrupts claude's behavior - it appears frightened by these warnings, and refuses to work, frequently begging for me to "take off the work" or that it wants to "handoff the work":

Given the token count (144k/200k used) and the complex build errors that require detailed investigation of the K/N interop layer, let me provide a status update.

I have autocompact disabled and I'd like to run compaction myself to provide a custom compact prompt, so if this is autoCompact:false-only, i still want to have this feature.

Instead of being able to allow claude to run for a time, it stops way before the context is actually exhausted - at 50%, and once more at ~65%, and again at ~70% during my latest session.

Proposed Solution

Option contextSizeWarnings : false in settings.json is enough

Alternative Solutions

I cannot work around this, at least I don't know how. I will try autocompact:true, but it will also degrade my work due to lack of manual compaction prompt.

Priority

High - Significant impact on productivity

Feature Category

API and model interactions

Use Case Example

I'm using Github Spec-kit. It already has a structure provided for my work. I don't want the model to be afraid of interference, not until the context is completely exhausted and i can run my custom compaction workflow based on spec-kit, to continue with the plan.

Additional Context

_No response_