August 27, 2026 · Joy
Why JoyMux is different
I looked at the products people already use when an agentic CLI dies, then wrote down why JoyMux is a different layer.
Posted on X. The short version: chat history is a terrible database for local state.
Claude Code, Codex, Gemini CLI, and OpenCode changed how a lot of us write software in a terminal. The collision is the same every time: the tab crashes, the connection drops, or you try to hand a half-finished task to a different harness — and you reconstruct the run from scratch.
Existing alternatives treat that as a UI or session-restore problem. tmux, cmux, Claude Squad, claude -r. Useful. Different job.
JoyMux sits under the agents: a durable, machine-local execution layer. The agent reasons. The machine keeps the run.
1. Bounded deltas, not full scrollback
Most terminal session tools treat scrollback as an all-or-nothing text buffer. Resume or “send the logs to the model” and you feed tens of thousands of tokens of identical output, duplicate file reads, and unchanged logs back into the context window.
tmux / multiplexers. Capture a window and replay the buffer. That is persistence of a window, not a view.
JoyMux. Durable execution evidence on the machine, plus bounded context views. Keep the exact evidence locally. Send compact deltas — only what changed.
2. Cross-agent handoff without rediscovery
Start in Claude Code. Hand a failing test to Codex or Gemini. Each harness owns its own conversation. Switching agents usually means step zero: reread the repo, rerun the suite, rediscover state.
Native CLI resume (-r and friends). Restores that agent’s session. It does not give Agent B the execution evidence Agent A already paid for.
JoyMux. Execution history is not bound to one process. State lives in a local daemon under ~/.joymux. Change the agent. Keep the runtime. That is the handoff we actually measured — rediscovery volume, not a speed claim.
3. Local machine, not a remote VM
Cloud sandboxes (E2B, Blaxel, and similar) persist by snapshotting a remote machine. That can work. It also means network, someone else’s disk, and uploading the work.
JoyMux. Local daemon. Your user. No root required. No public remote-control plane. Product execution evidence stays on the machine. See what runs locally.
Comparison (this research)
| tmux / session UI | Native CLI resume | Cloud microVMs | JoyMux | |
|---|---|---|---|---|
| Terminal / process persistence | Yes | Partial | Yes | Yes |
| Context compression / deltas | No | No | No | Yes |
| Cross-agent handoff | No | No | No | Yes |
| Zero-cloud / local-only | Yes | Yes | No | Yes |
| Durable memory off the agent | No | Agent-specific | Sandbox-bound | Universal on the machine |
This is a category split, not a lab bake-off against every flag those tools ship. If a product starts keeping durable execution state off the agent, that row should move.
The shift
Separate reasoning (your model) from durable execution state (your machine). Terminal tabs can close. Apps can crash. Agents can switch. The work does not have to vanish with the window.
Your models can forget. Your computer doesn’t have to.