2
1 Comment

The context window is not your working memory

While building TokenBar, I noticed a weird behavior change in my own AI workflow.

As context windows got bigger, I got sloppier.

I stopped restarting chats.
I pasted in more raw tool output.
I carried old requirements and dead-end reasoning much longer than I should have.

Nothing looked broken, so it felt efficient.

It was not.

Three things got worse:

  1. Review got slower
    The model had more baggage, so I had more baggage to reread too.

  2. Prompt quality dropped
    I relied on the model remembering old context instead of stating the current task cleanly.

  3. Spend got harder to predict
    One long chat quietly turned into the default workflow.

What actually helped was not another after-the-fact dashboard.

It was seeing token usage live while I worked.

Once I could see the token trail in real time, I started using it as a workflow signal:

  • restart instead of dragging stale context forward
  • summarize logs instead of pasting everything back in
  • stay on a smaller model until the task really needs more context

Big context windows are useful.
But they are easy to mistake for permission to be messy.

That lesson is a big reason I built TokenBar for macOS.
https://tokenbar.site/

on May 10, 2026
Trending on Indie Hackers
I Was Picking the Wrong SaaS Tools for Two Years. Here's the Mistake I Finally Figured Out. User Avatar 81 comments Drop your landing page URL. I'll use Ferguson to tell you why visitors might be leaving User Avatar 61 comments AI helped me ship faster. Then I forgot what my product actually does. User Avatar 39 comments Most early-stage SaaS companies miss churn signals — here’s how to catch them early User Avatar 31 comments Why Remote Teams Stop Talking (And Don't Even Notice It) User Avatar 22 comments How I Run a 1.7M Product Search Engine at 66ms on a $0 Hosting Budget User Avatar 19 comments