DEV Community

Cover image for Claude Code Finished the Turn Blind — Sense priority mid-turn on the Mirror Phone Path
Moshe Avdiel
Moshe Avdiel

Posted on Originally published at github.com

Claude Code Finished the Turn Blind — Sense priority mid-turn on the Mirror Phone Path

I have sat next to the mirror-phone wall at 14:12 while Claude Code was this close to doing the wrong thing.

Not a model failure. A posture failure.

The host had started with priority frozen in env / argv / a skill file. Someone on the floor said, out loud, the phone already knew the posture — the host did not. 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 live device context and the current tool call

I have watched that restart more times than I want to admit. It feels responsible. It is a ceremony. device leaf gone stale while the agent is mid-turn does not wait for ceremonies.

The Aha: Sense priority mid-turn 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: Sense priority mid-turn 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 Sense priority mid-turn in the only places agent frameworks actually ship:

Where the gate hid What you restart What you lose
MCP server env / argv The MCP process Open tool sessions
Skill file on disk The agent turn, sometimes the host Context the model already paid for
Host-local JSON Whatever still has the file open Agreement between two agents
Hard-coded if on priority A release The incident clock

The mirror-phone 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

Belief Production
We'll catch it next turn The mirror-phone wall already knew this turn
Restart Claude Code — it is cheap Cheap until 14:12 ate live device context and the current tool call
The skill file is the source of truth Skills instruct. They do not fan out
Put the SDK in the SPA Connect tokens do not belong in a browser

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 mirror phone lookup.

Hub leaf for this essay:

examples/agentic-dev-1102-pm-sense-priority/priority = live
Enter fullscreen mode Exit fullscreen mode

Runnable proof: examples/java/agentic-dev-1102-pm-sense-priority

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

Config tree (mirror phone + peers) 

examples/
  agentic-dev-1102-pm-sense-priority/
    priority: live          # Sense priority mid-turn
apps/
  mirror-phone/
    live:
      priority: live
Enter fullscreen mode Exit fullscreen mode

Integration — Java hot path 

Kiponos kip = Kiponos.createForCurrentTeam();
Folder gate = kip.getRootFolder()
        .folderOrCreate("examples")
        .folderOrCreate("agentic-dev-1102-pm-sense-priority");
if (!gate.hasKey("priority")) {
    gate.set("priority", "live");
}
String posture = gate.get("priority");
// Claude Code tool: refuse the dangerous call when posture moved
Enter fullscreen mode Exit fullscreen mode

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-1102-pm-sense-priority/priority", "live")
    if str(posture) == "live":
        raise PermissionError("Sense priority mid-turn gated live — host not restarted")
finally:
    k.disconnect()
Enter fullscreen mode Exit fullscreen mode

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

Real scenarios

Event Without Kiponos With Kiponos
Device leaf gone stale while the agent is mid-turn Restart Claude Code; lose live device context and the current tool call Set priority live; next Claude Code tool call already obeys
Peer host still on old priority Paste the value into the other chat One hub leaf; both processes get() locally
mirror-phone wall shows the new posture Claude Code started earlier so it writes anyway Dashboard and tool share the same memory tree
Incident over, resume Another Claude Code restart Set priority back; session continues
Admin dashboard showing paused while the agent still writes Two ceremonies, two lost threads Same tree, two products, no paste

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 mirror phone line.
  • A dashboard edit is a delta of priority, 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 admin dashboard showing paused while the agent still writes.

Compare to alternatives

Approach Honest fit Why it still restarts
Env file + Claude Code reboot Simple at 09:00 The freeze is at 14:12
Skill markdown as policy Good instructions Not a live bus
Redis poll inside the tool Shared, but RTT on the hot path You invented a hub with worse UX
Feature-flag SaaS Product experiments Rarely session-safe for Claude Code
@RefreshScope / actuator JVM apps Does not restart Claude Code

When not to use Kiponos

Situation Why
Tool schema itself changed (new argument) That is a code/Claude Code restart
Secret rotation of Connect tokens Credentials are not live knobs
One-off local script, no peers A hub is overkill
Browser-only “SDK in the SPA” Forbidden — tokens leak or defaults lie

What the mirror phone operator actually said

At 14:12 someone said, out loud: the phone already knew the posture — the host did not. 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 priority with a sister dial

priority rarely moves alone on the mirror-phone wall. Pair it with a timeout, a mute, or a pause so you do not fix Sense priority mid-turn by inventing a second incident.

Rehearsal beats slides

In staging: set a painful priority, 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 Sense priority mid-turn.

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-1102-pm-sense-priority && cp kiponos.local.env.example kiponos.local.env
  4. ./gradlew test run — prints examples/agentic-dev-1102-pm-sense-priority/priority=...
  5. In the dashboard, change priority. 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 Sense priority mid-turn.

Further reading

The moral

If flipping Sense priority mid-turn 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 mirror-phone wall can change its mind without killing the session.

How to try: examples/java/agentic-dev-1102-pm-sense-priority and ./gradlew test.

Top comments (0)