Hidden conversation limits cause unexpected session terminations despite token budget showing 70% remaining

Resolved 💬 3 comments Opened Oct 19, 2025 by joooneyd Closed Jan 10, 2026

I'm a paying subscriber (/month) experiencing a critical UX issue with Claude Code's token limits.

The Problem

Yesterday, Claude Code repeatedly showed me I was only using ~30% of my token budget, yet terminated my session claiming I'd reached "session limit." There are apparently TWO separate limits:

  1. Per-message token budget (visible - 200K tokens)
  2. Total conversation length (hidden - no visibility)

Why This Is Unacceptable

  • No warning before session termination
  • No way to plan work sessions
  • Wasting paid subscription time on unexpected cutoffs
  • Claude shows "plenty of tokens remaining" then abruptly ends
  • Zero transparency on the actual limit causing termination

What I Need

  1. Visible conversation length counter - show me BOTH limits
  2. Warnings at 75%, 90%, 95% of conversation limit
  3. Clear documentation of what counts toward each limit
  4. Predictability for a paid product

If this isn't addressed, I will cancel my subscription. I'm paying for a professional tool, not a guessing game.

View original on GitHub ↗

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