@linkshell/host
The LinkShell v2 host daemon. It runs on your computer and owns what your devices control: agent sessions (Codex, Claude Code, Gemini, Copilot, Grok and other ACP agents), terminals, files, port previews and the remote screen. Devices reach it over the LAN or through a relay, end-to-end encrypted.
Run it through the CLI: npm install -g linkshell-cli, then linkshell host --daemon.
Claude Workflow progress and background sub-agent transcripts stay synchronized even while the main conversation is idle. The app can open each run, phase and Agent independently.
Codex authentication
Codex uses the computer's existing ChatGPT, API key or custom-provider configuration, including settings managed by CC Switch. A Codex login is not required by LinkShell: account detection is advisory, and Codex reports credential errors when a request runs. Restart the host after changing shell environment variables.
pnpm --filter @linkshell/host live:codex-api checks the installed Codex CLI against a
loopback Responses fixture with isolated configuration: saved API keys, provider env keys
and providers without account authentication. Each completes two turns through the host
and checks HTTP authentication. No real API credentials or paid inference are used.
Session recovery
Host 0.4.19 revalidates busy sessions after restart, reconciles Codex native archives, and treats interrupted turns as finished. Archived Codex history is read without unarchiving. Missing Claude transcripts and other history failures preserve cached messages and show a retryable error. Lazy ACP agents initialize before their restore capabilities are checked; resume-only agents explain that earlier messages cannot be fetched.
The host negotiates and validates ACP 1. ACP 2 remains draft and changes prompt completion, history replay, messages and permissions; changing the version number alone is incompatible. See session recovery, protocol evidence and validation.
Agent questions
Codex Desktop asynchronous questions retain their pending state and accept immediate replies. Claude and standard ACP forms, Cursor choice questions, and Grok questions/MCP forms share the phone's question card while preserving each agent's native response format. See question support and validation boundaries.
Remote screen
screen.start returns a token-protected loopback viewer port and display list. The phone
forwards the port; the web client hosts the same page in an isolated iframe. On Apple silicon and Intel
Macs running macOS 13+, the universal LinkShell.app captures and encodes with ScreenCaptureKit/VideoToolbox. The host passes
SDP/ICE over its Unix socket; the media track and four input/cursor channels run directly
between LinkShell.app and the native iOS receiver or web player.
This media connection is separate from the host's werift bulk DataChannel (direct.offer),
which can carry forwarded HTTP/WebSocket traffic. If video fails, the Mac supplies encoded
H.264 frames over another Unix socket and screen-pacer.ts applies ACK-based dropping and
quality steps; WebCodecs renders the byte stream. iOS tries native → standard WebView → RPC,
bypassing the bulk direct channel for the last step. Linux uses ffmpeg/X11 and is view-only.
LINKSHELL_ICE_SERVERS=off disables the bulk channel and removes STUN from screen signalling;
video can still try LAN candidates. LINKSHELL_SCREEN_VIDEO=off disables media-track offers.
A gateway with a TURN server lends the host its credentials (turn.credentials): video tries
direct paths first, the relay next (held to the gateway's TURN_MAX_KBPS), and the byte relay
last. A relayed picture, through TURN or the gateway, ends after 3 minutes unused
(LINKSHELL_SCREEN_IDLE_SECONDS, 0 for never); LINKSHELL_TURN=off keeps the host off TURN. See the current architecture for
source/display limits, transport-specific defaults and validation boundaries.
Requires Node.js 22.13 or newer.
MIT License