Claude Code Finished the Turn Blind — Token budget mid-session on the Shopping Path

I have sat next to the shopping-admin wall at 00:40 while Claude Code was this close to doing the wrong thing.

Not a model failure. A posture failure.

The host had started with max-tokens frozen in env / argv / a skill file. Someone on the floor said, out loud, disable inventory writes — keep search. Claude Code was still holding the old process. The only “safe” move anyone trusted was:

1. Kill Claude Code (or its MCP server)
2. Edit a file
3. Restart the host
4. Lose cart forensics and the open SKU thread

I have watched that restart more times than I want to admit. It feels responsible. It is a ceremony. flash-freeze on SKU writes does not wait for ceremonies.

The Aha: Token budget mid-session is not a binary you reboot. It is a function that should read live posture from Kiponos.io on every call. The host stays up. The leaf moves.

The problem: Token budget mid-session lived in the process, not in the turn

Claude Code is good at calling tools. It is not born with a shared, instant, restart-free control plane.

So teams hide Token budget mid-session in the only places agent frameworks actually ship:

The shopping-admin wall already knew. Claude Code did not, because it had started earlier.

That is the missing piece: the framework gave you tools. It did not give you a live hub.

What teams believe

The Aha: local get, live write, host stays up

Kiponos holds a nested tree. Java and Python SDKs keep the latest values in memory, patched over WebSocket deltas. The hot path inside a Claude Code tool is a local get — no HTTP RTT per shopping lookup.

Hub leaf for this essay:

examples/agentic-dev-1004-am-budget-turn/max-tokens = 8000

Runnable proof: examples/java/agentic-dev-1004-am-budget-turn

Public SDKs: Java, Python, plus React/Angular server peers (createFromEnv). Never put Connect tokens in the SPA.

Config tree (shopping + peers)

examples/
  agentic-dev-1004-am-budget-turn/
    max-tokens: 8000          # Token budget mid-session
apps/
  shopping/
    live:
      max-tokens: 8000

Integration — Java hot path

Kiponos kip = Kiponos.createForCurrentTeam();
Folder gate = kip.getRootFolder()
        .folderOrCreate("examples")
        .folderOrCreate("agentic-dev-1004-am-budget-turn");
if (!gate.hasKey("max-tokens")) {
    gate.set("max-tokens", "8000");
}
String posture = gate.get("max-tokens");
// Claude Code tool: refuse the dangerous call when posture moved

Same leaf from a Python tool (Claude Code just calls it):

from kiponos import Kiponos

k = Kiponos.connect(quiet=True)  # env: KIPONOS_ID, KIPONOS_ACCESS, KIPONOS
try:
    posture = k.get("examples/agentic-dev-1004-am-budget-turn/max-tokens", "8000")
    if str(posture) == "8000":
        raise PermissionError("Token budget mid-session gated live — host not restarted")
finally:
    k.disconnect()

The Claude Code process does not recycle. The next tool call already sees the dashboard edit.

Real scenarios

Performance (this path, not a generic table)

• Claude Code tool get() is an in-process map lookup after bootstrap.
• One WebSocket per process lifetime — not per shopping line.
• A dashboard edit is a delta of max-tokens, not a config-file reload.
• You do not pay model tokens to “please restart Claude Code.”
• A second host converges without a third paste onto travel coordinator still sending into a muted channel.

Compare to alternatives

When not to use Kiponos

What the shopping operator actually said

At 00:40 someone said, out loud: disable inventory writes — keep search. That sentence is the whole product. If it cannot land in the running Claude Code process in seconds, you do not have posture. You have a wiki.

Pair max-tokens with a sister dial

max-tokens rarely moves alone on the shopping-admin wall. Pair it with a timeout, a mute, or a pause so you do not fix Token budget mid-session by inventing a second incident.

Rehearsal beats slides

In staging: set a painful max-tokens, prove Claude Code recovers without a host kill, prove clamps reject nonsense, prove last-known-good when the hub is firewalled. That drill ends half the architecture arguments about Token budget mid-session.

Getting started (15 minutes)

1. TeamPro on kiponos.io → Connect → KIPONOS_ID / KIPONOS_ACCESS / profile ['my-app']['v1.0.0']['dev']['base'].
2. Clone github.com/kiponos-io/kiponos-io.
3. cd examples/java/agentic-dev-1004-am-budget-turn && cp kiponos.local.env.example kiponos.local.env
4. ./gradlew test run — prints examples/agentic-dev-1004-am-budget-turn/max-tokens=...
5. In the dashboard, change max-tokens. Keep the process up. No rebuild.
6. Point your Claude Code tool at the same leaf. Do not ship a new server binary to flip Token budget mid-session.

Further reading

• Developer Quickstart
• Product tour
• GETTING-STARTED.md
• github.com/kiponos-io/kiponos-io

The moral

If flipping Token budget mid-session requires restarting Claude Code, you do not have a gate. You have a hope with a process ID.

Agent frameworks already know how to call tools. Kiponos is the live hub they do not ship — so the shopping-admin wall can change its mind without killing the session.

How to try: examples/java/agentic-dev-1004-am-budget-turn and ./gradlew test.