Keep Claude Code Remote Control alive across reboot with an OS supervisor

Leandro Cannizzaro — Sun, 11 Oct 2026 18:59:41 +0000

Claude Code Remote Control is useful from the phone or claude.ai — until the terminal on the machine dies. Close the window, crash, sign out, or reboot, and the remote client loses the session.

I built LiveClaude to treat those sessions like infrastructure instead of a leftover terminal window. I'm the author.

The gap

Remote Control (and Cursor My Machines workers) run as foreground processes. That is fine for a short interactive session. It is a bad fit if you expect the machine to stay reachable overnight or after a restart.

People usually invent one of:

leave a terminal window open and hope
wrap the CLI in tmux + a personal script
hand-write a systemd unit / Scheduled Task

Those work. They also do not give you a multi-session UI, product-aware flags, or a place to complete the one-time trust/login prompts that need a real terminal.

What LiveClaude does

LiveClaude is an MIT open-source supervisor + Avalonia desktop app, written entirely in C# / .NET (no Node, Python, tmux, or browser automation):

one long-lived process per project/session
OS-native restart: Windows Scheduled Task / Service, Linux systemd, macOS LaunchAgent / LaunchDaemon
desktop UI to create/edit sessions, watch state/logs, install or remove the supervisor
embedded real pty (ConPTY on Windows) + a VT emulator in C# for trust / login / attach

Same idea for Cursor My Machines workers when you want the same restart policy.

Install

# Windows
winget install LeandroCannizzaro.LiveClaude

# Linux
curl -fsSL https://leandrocannizzaro.github.io/LiveClaude/install.sh | sh

# macOS
curl -fsSL https://leandrocannizzaro.github.io/LiveClaude/install-macos.sh | sh

Repo: https://github.com/LeandroCannizzaro/LiveClaude

Product page: https://leandrocannizzaro.github.io/LiveClaude/

Requirements (honest)

Windows 10 1809+ / 11, Linux with systemd, or macOS 12+
Claude Remote Control still needs Claude Pro/Max/Team/Enterprise (API-key-only Remote Control is not supported upstream)
Prefer a native claude install stable path over a desktop-bundled CLI when you can

Why bother with a dedicated app

The interesting part is not "run a process forever." It is combining:

restart policy at the OS level
multi-session management in one UI
an attachable terminal for the prompts you cannot fake with a headless wrapper

If you already solved this with a unit file and are happy, keep it. If you keep losing Remote Control after a reboot, LiveClaude might save you an afternoon.