Why "Reconnecting" Is the Wrong Abstraction

"Reconnect" is a network concept. Resume is a work concept. If you optimize for reconnecting, you still lose state and output.

The better abstraction

• Session identity stays stable.
• Output replay fills the gap.
• Resume becomes the default action.

Why this matters

When the system treats the session as durable, you stop thinking about the network. You just keep working.

Link up

• Remote Development Without Reconnect Friction: /remote-development-without-reconnect-friction/
• Persistent Dev Environment: /persistent-dev-environment/
• Phone Terminal Codex: /phone-terminal-codex/

Related reads

• /why-ssh-drops-break-deep-work/
• /latency-vs-continuity-remote-dev/