Deep Culture · Understanding Political Economy

Every token, every time

A language model has no memory between steps: to produce each response it re-reads its entire context — system prompt, your messages, its own thoughts, every file it opened. Press play and watch what a coding agent actually bills you for.

Scenario

Context window

now holding 0 tokens
re-reading full context
Pick a scenario and press play.
Billed input tokens
0
re-sent context, cumulative
Output tokens
0
thoughts · tool calls · replies
Running cost
$0.00

Session log

Transcript vs. what you pay for

cumulative billed input transcript size
0 / 0
Configure the custom scenario
Hidden instructions sent with every single request.
Your question, in tokens.
Reasoning the model writes before acting.
Each tool call dumps a file into the context — for good.
Drag this up and watch the cost curve bend.
Each “now you broke it again” repeats the whole cycle on a bigger context.

Background — why this happens

1

A token is a word, or a piece of one

Language models don't read letters or words — they read tokens: frequent chunks like “the ”, “cat”, or “();”. Roughly ¾ of an English word each. Everything a model reads and writes is counted in tokens, and tokens are what you're billed for: typically a few dollars per million in, and about five times more per million out.

2

No memory between steps

A model doesn't “remember” the conversation the way you do. It's autoregressive: to produce anything, the entire context — system prompt, your messages, its own thoughts, every file it opened — is fed through the model again. Nothing is held over; everything is re-sent, every request.

3

Agents make it explode

A chatbot re-reads a few thousand tokens. A coding agent makes tool calls that dump whole files into the context — and they never leave. Each new step re-reads everything before it, so total billed input grows roughly with the square of the session. A real six-prompt vibe-coding session can bill ~2 million input tokens for ~47 thousand tokens of actual output.

4

Caching softens it — it doesn't solve it

Providers re-charge already-seen context at ~10% of the price (prompt caching). That helps a lot — toggle it above and watch the cost drop. But caches expire within minutes, the context still fills up, and the re-reading still happens. This is why flat-fee agentic coding plans were quietly subsidised, and why usage caps and per-token pricing arrived.