1
0 Comments

Your context window is a budget, not a trophy

When I started using models with huge context windows, I assumed bigger meant easier.

What actually happened was I stopped noticing waste.

I would keep old specs, tool output, stack traces, and half dead prompts in the session because the model could still handle it.

The result was not just higher spend. It was slower decisions.

The pattern I watch now is simple: if the context window keeps growing but the task is not getting clearer, the session is probably getting worse.

A few habits that changed my workflow:

  • start a fresh session when the task changes
  • summarize the useful bits instead of dragging the full transcript forward
  • keep logs and large outputs out of the main chat unless I need them
  • stay on smaller models until the hard step actually arrives

That is why I built TokenBar for macOS.

It keeps live token usage visible in the menu bar while I work.

For me, token counting is less about billing and more about knowing when my workflow is drifting.

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 70 comments I built a tool directory that doesn't pretend every founder has the same needs User Avatar 64 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 How I Run a 1.7M Product Search Engine at 66ms on a $0 Hosting Budget User Avatar 19 comments