Share a Local Thread
Share a conversation and work against a folder on its host computer.
Local Threads run on their host computer. A Workspace can contain both shared Local Threads and Cloud Threads.
How the connection works
- The Thread's host enables Allow members to join in its More options menu.
- The conversation is synchronized for Workspace members. Live execution is available while Worktree remains open on the host computer.
- An invited guest connects with a short-lived credential.
- An authenticated relay forwards encrypted WebSocket traffic between the owner and guest without storing the repository.
- Short-lived credentials renew while both Desktop clients remain active.
The host works directly in the selected folder. Guests can read synchronized history while the host is offline. Commands, files, review, and terminals require the live host connection. History syncs periodically while Worktree is open; messages not yet synchronized become available after the host reconnects.
What is billed
Local sharing costs $0.10 per active remote guest-hour, charged to the Thread host. The host does not consume guest time. Two active guests for 30 minutes use one guest-hour. Reading saved history offline does not open a guest connection.
Free includes a restricted $5 Local Sharing credit each month, approximately 50 active guest-hours. Free permits one concurrent guest, two actively shared Local Workspaces, and three invited members per Workspace.
Presence
Worktree shows who is in the current Thread. A focused Thread is shown as active. A visible but backgrounded Thread remains present with a background status for a short grace period; disconnected or stale clients move offline.
Turn sharing off
Disabling sharing invalidates new joins and active relay authorization. Members remain in the Workspace, but this Thread's history and execution are unavailable to them until its host enables sharing again.
