Detach and Reattach Sessions: The Killer Feature for Moving Between Devices
Imagine running a complex Claude Code edit on your desktop, but halfway through the agent’s work, you need to leave for a meeting. Without a tool like Clusto, you either wait, cancel, or lose progress. With Clusto, you simply walk away. Your session stays alive on the server. Later, you open the Clusto app on your phone or laptop, reconnect, and pick up exactly where you left off. That is the core promise of being able to detach and reattach sessions.
This is not a futuristic dream. It is a practical workflow shift for any developer who uses terminal-based AI agents or shells. Clusto runs sessions on your own machine, but keeps them alive independent of your client. Disconnect, switch devices, and the session keeps ticking. The state is preserved, the output is recorded, and your agent does not miss a beat.
How Detaching Changes Your Daily Workflow
Most developers accept that closing a laptop lid means killing active terminal commands. Clusto removes that limitation. By moving sessions to a server-side process, you gain real freedom of movement.
Step-by-step: What detaching looks like in practice
- Start a session as usual on your desktop: launch Claude Code, Codex, or a shell through Clusto.
- Close the app or switch devices without stopping the agent. The session is detach and reattach sessions ready.
- Reconnect from another device (phone, tablet, laptop) and resume exactly where the session was.
This works for single-user scenarios and extends to team contexts when you share a Clusto node.
The real benefit: uninterrupted agent work
AI coding agents can run for minutes or hours. Being able to detach and reattach sessions means you can start a long-running refactor on a powerful workstation, then check its progress from a quiet corner on your tablet. You are never tied to one desk.
Where Sessions Live: Server vs. Client
Traditional terminal tools tie a session to your client. Close PuTTY, SSH, or iTerm2, and the session ends. Clusto breaks that link.
| Aspect | Traditional terminal | Clusto session |
|---|---|---|
| Session location | Lives in client app | Lives on server (your own machine) |
| Client disconnects | Kills session | Session stays alive |
| Reattach from another device | Requires starting over | Resumes exact state |
| Output persistence | Lost | Recorded for review |
This architecture makes cross-device movement natural. You never lose your terminal state. Your coding agents keep running. The Clusto Documentation describes the underlying mechanics in detail.
Practical Use Cases for Moving Between Devices
Scenario 1: Desk to coffee shop
You are on a coding agent that is working through a test suite. Your laptop is overheating. Instead of waiting, you detach, grab your phone, and walk to the cafe. From the Clusto web app on your phone, you reattach and monitor progress.
Scenario 2: Office to home
At the end of the workday, you detach a running shell script on your office Linux box. At home, you reconnect from your personal Windows laptop and review the output. The session never paused.
Scenario 3: Pair debugging with a teammate
On a multi-seat license, you can share a node. Start a session on a shared server, detach after your shift, and let a teammate reattach to continue the same debugging session the next morning.
What Technology Makes This Possible
Clusto runs a lightweight daemon on your server machine. The daemon manages session lifecycle. When a client connects, it streams output. When the client disconnects, the daemon keeps the process alive in the background. Reconnection restores the view to the last line of output.
This is similar to GNU Screen or tmux, but with three critical improvements:
- Native integration with AI coding agents (Claude Code, Codex, Copilot)
- A clean native app for Windows, Linux, and Android, plus a web app for all platforms
- Automatic discovery of nodes on the same Tailscale network
To get started quickly, use the installation guide to set up Clusto on your machines in minutes.
Is This Feature Secure?
Security is built into the detach and reattach sessions model. The session data never leaves your own machine. Clusto simply manages client connections. Authentication is handled through a license key (HIVE-XXXX-XXXX-XXXX) and optional Tailscale integration for network-level security.
No third party stores your terminal output. No cloud intermediary holds your session state. You own the machine, you own the session.
Getting Started with Clusto
If the idea of detach and reattach sessions appeals to you, the setup is straightforward:
- Install the Clusto daemon on your server (Linux, macOS, or WSL) with a single curl command.
- Install the Clusto app on your devices from the download page.
- Activate your license (free Personal plan supports up to three devices).
- Connect to your node and start detaching.
Once set up, the workflow becomes second nature. Start a session on your desktop, walk away, come back on your phone. Your coding agents never stop working, and you never lose your place.
Try it yourself
Clusto provides a killer feature that turns device-switching friction into a seamless transition. Stop letting your hardware dictate when you work. Start your first session today and detach freely.
Frequently asked questions
What does it mean to detach and reattach sessions in Clusto?
It means your terminal session or coding agent continues running on the server even after you close the app on one device. You can reconnect from any other device and see the exact same state, including live output and running processes.
Can I use detach and reattach sessions with any coding agent?
Yes. Clusto works with Claude Code, Codex, GitHub Copilot, OpenCode, and plain shell sessions. As long as it runs in your terminal, you can detach and reattach.
Do I need a paid plan for the detach and reattach sessions feature?
No. The free Personal plan supports up to three devices and includes the full detach and reattach sessions functionality. Paid plans add multi-seat team access.
Is my session data stored on a third-party cloud?
No. Sessions run on your own machine (server). Clusto only manages the client connection. No session data leaves your control.
How do I install Clusto to start detaching sessions?
Install the daemon on your server with the one-line curl command from the Clusto website, then install the app on your devices. The setup wizard guides you through the process.