BasicAgent
Why tmux Isn't Enough Anymore
tmux keeps shells alive, but it doesn't solve output replay, session identity, or reconnect friction on its own.
Published: 2026-01-04 · Last updated: 2026-01-04
tmux keeps shells alive, which is useful. But it does not solve the full continuity problem by itself.
Where tmux falls short
- Reconnect friction still happens in the client.
- Output replay across device switches is inconsistent.
- Session identity is not built for multi-device workflows.
What continuity requires
A durable terminal workspace needs more than a server-side multiplexer:
- resumable sessions,
- replayable output,
- stable session identity across clients.
Link up
- Always-On Terminal Workspace: /always-on-terminal-workspace/
- Persistent Dev Environment: /persistent-dev-environment/
- Phone Terminal Codex: /phone-terminal-codex/
Build narrative
Follow a coherent path from thesis to lab notes to proof-of-work instead of isolated pages.
Step 1
Intelligence systems office
The strategic map for what is being built and why.
Step 2
Lab notes
Build footprints and progression logs as proof-of-work.
Step 3
Control surface
Governance and monitoring architecture for operational reliability.
Step 4
Private alignment
Convert insight into execution with scoped collaboration.