Repository navigation
Restore the composer context window indicator as an optional setting #33639
Description
What happened
Please add back the composer's context window display as a setting. It was a legacy option, and it was recently removed.
Diagnosis
This is an intentional removal, not a regression. #33131 deleted ContextWindowMeter, its composer wiring, and the contextWindowMeterEnabled setting. The PR's reason is that Thread details already shows context usage.
The Thread details item does not fully replace the meter:
- The meter was in the composer footer. The replacement is a row in the Thread details card.
- The meter's hover popover had a Compact context button for providers that support compaction. That button is gone, and users now have to send
/compact. - The popover also showed total processed tokens and cost when available.
ThreadDetailsContextshows only context usage and the auto-compaction threshold. contextWindowMeterEnabledwas not migrated. The Thread details Context window item defaults to off and only inherits fromthreadDetailsUsageEnabled, so people who had the meter on lose context usage until they find the new setting.
The web client still receives this usage snapshot for Thread details, so restoring the meter behind a client setting should not need a server change.
Requested: bring back the meter behind a setting, off by default as before, including its Compact context action.
Steps to reproduce
- Run a build that includes feat(settings): clean up Labs: promote tool calls, remove plan mode and old toggles #33131, such as v0.1.8.
- Open Settings → Labs. The Context window indicator toggle is gone.
- Open a thread whose provider reports context usage.
- The composer footer shows no context window indicator, and no setting brings it back.
Version
0.1.9-nightly.20261109.4443 (removal also present in v0.1.8)
Environment
Windows 11 x64, T3 Code Nightly desktop app, Node 26.13.0
Evidence
#33131, merge commit 521ac7c218b3faa74281fb72fc36ce74a0951fb3:
deleted apps/web/src/components/chat/ContextWindowMeter.tsx (-180)
deleted apps/web/src/components/chat/ContextWindowMeter.logic.ts (-85)
removed contextWindowMeterEnabled from packages/contracts/src/settings.ts
Replacement on main, apps/web/src/components/chat/threadDetailsItems.ts:
{ id: "context", label: "Context window", defaultVisible: false }Related issues
#33131 removed it. #26499 asked to make it a regular setting and is closed. #9190 made it opt-in. No open issue requests restoring it.
Fix applied or workaround
Nothing was changed on the machine. Partial workaround: turn on Settings → Appearance → Thread details → Context window, and send /compact manually.
Filed by
claude (claude-opus-5-5) in T3 Code, following the t3 triage playbook
Activity
bermudi commentedon Nov 10, 2026
Holy shit Theo, not everyone is you. Stop trying to force everyone to do things EXACTLY how you want them done. LET US MANAGE OUR OWN DAMN CONTEXT!!! NOT EVERYONE CAN SPEND THOUSANDS ON SUBSCRIPTIONS AND WASTE MONEY LIKE THERE IS NO TOMORROW
@t3dotgg
arandomhooman commentedon Nov 10, 2026
Yeah that but a lil less agressive. I really really wanna know what context I'm at. Likeee, this is doubly true on cheaper plans. I don't mind resuming a cold thread at 50-100k context but if it's 300k I'd rather make a new one. This is such a simple thing to have and doesn't interfere, would really like it back.
Theo, I get you got like 5 Ultra subs. But not all of us do :/
P.s. while we wait for this to probably get closed (lol) if you got to settings -> appearance -> thread details you cna make the context window appear there. Annoying, off by default, and less intuitive, but ig it exists :/
arandomhooman commentedon Nov 10, 2026
@juliusmarminge @maria-rcks I mean you could also bring this back 💔
YPQuinn commentedon Nov 10, 2026
couldn't agree more, I really need this indicator.
mgabor3141 commentedon Nov 10, 2026
This could have been a settings migration at least, I didn't know that this was an option in thread details.
That said, I would like to see it in the "normal spot" if possible. Also on mobile.
I agree that this doesn't belong in Labs (which was the point of the PR, it just overextended a little bit it seems). Should have moved it to Chat and/or Appearance just like tool calls. Unlike Plan mode this has barely any development/complexity overhead to keep around.
Please?
t3dotgg commentedon Nov 10, 2026
Right click the thread detail card.
I'm not clogging up the composer for this stupid indicator anymore.
t3dotgg commentedon Nov 10, 2026
@bermudi you in particular should uninstall our software. I will ban you from the repo if you ever leave a comment like this again.
You spent actual time being a dick to me personally for giving out software I could charge millions of dollars for for free. You spent zero time checking if there was an alternative option in the software.
You're an ungrateful prick who is lazy as shit, and I do not care about your opinions. If you don't like me for cleaning up messes, you should go use some closed source messy software that never gets updated. Will fit you much better :)
kevin-stuart commentedon Nov 10, 2026
Hey Theo (@t3dotgg), just to let you know, I liked and preferred having the little bubble there. The card is not visible if the width is not wide enough. It was an option for a reason. I would be in the "please" camp such as mgabor3141 as well.
I concur that this would belong outside of labs and more in appearance. I feel you were a bit heated in the discussion with your bias, but from a more objective standpoint, I think there are people that like having this and reason for having this as an option instead of imposing a preference on everyone does feel like the worse option. Please reconsinder how this is handled.
Thank you for having build T3 code with the thoughtful features and you and your teams hard work.
arandomhooman commentedon Nov 10, 2026
Could we get smth like it on mobile perchance 🥺
lAiasu commentedon Nov 10, 2026
I don't usually whine at UI changes but this is an absolutely baffling decision.
bermudi commentedon Nov 10, 2026
I was out line. I have no problem accepting that.
In my defense it is really hard dealing with your aura of arrogance where everyone who disagrees with you is nothing but an idiot. I did check the release notes. Zero fucking mentions there. https://github.com/pingdotgg/t3code/releases/tag/v0.1.8
I did try to right click everywhere that occurred to me, unfortunately i didn't fucking think of right clicking the card because I'm not theo therefore I'm an idiot for not knowing the card is the only thing that is configured with right click and not in settings. I guess I should have launched 5 agents to search the codebase to make sure it was really, really gone before commenting. What an idiot.
Ban me, see how much I care. I've said my peace.
juliusmarminge commentedon Nov 10, 2026
Thanks for writing this up. It asks for new behaviour rather than reporting a defect, so it does not belong in the bug tracker and I'm closing it as not planned here. Feature ideas are discussed in Discussions: please post it there.
arandomhooman commentedon Nov 10, 2026
Not quite, this is an existing feature, not new. Just removed. All the confirmed working code for it exists and was in the project before.