[FEATURE] Lightweight Mac daemon with cross-client session discovery and continuation

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Feature request: Lightweight Mac daemon with cross-client session discovery and continuation

Problem

I use Claude Code on my Mac and want to continue the same work from other devices, including iOS. The workflow I value in Codex SSH mode is a lightweight, persistent daemon on the host and sessions that can be created through one channel, then discovered and continued through another. I would like an equivalent workflow in Claude Code, with session continuity independent of the client that started the session.

Requested behavior

Provide a lightweight background daemon on macOS that maintains persistent sessions and supports authenticated remote access, ideally over SSH or an equivalent secure connection. Any supported client—including the CLI, desktop, web, and iOS—should be able to discover and resume sessions on that host, regardless of where they originated.

Continuing a session should preserve its conversation, working directory, execution state, and permission settings. Disconnecting or closing a client should leave the session available for later reconnection. Execution should remain on my Mac, using its existing files, tools, and environment, without requiring a cloud-hosted copy of the workspace.

Practical benefit

I could start a task at my desk, check progress or respond to an approval request from my iPhone, and return to the same session on my Mac. This would eliminate repeated setup and context reconstruction while keeping my local machine as the execution host. The essential capability is durable session continuity across clients, with low background overhead.

Proposed Solution

Introduce an optional, lightweight macOS daemon that manages persistent Claude Code sessions independently of any client connection. The daemon would maintain a shared session registry so authenticated CLI, desktop, web, and iOS clients can discover and resume sessions created through any supported channel, preserving conversation history, working directory, task state, and permission settings. Remote clients could connect over SSH or an equivalent secure transport, while tools and file operations continue to run on the Mac. Client disconnections should not terminate sessions, and switching clients should transfer interactive control safely, preventing conflicting commands or duplicate execution.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

Other

Use Case Example

_No response_

Additional Context

_No response_