Share sessions
Choose who can open a session, keep it updated, and automate sharing by repository.
Each Sher link represents one root session and any subagent sessions it spawned. The link keeps the same audience and deletion lifecycle for the whole session tree.
Choose an audience
The session browser offers these choices when you press s:
| Audience | Who can open it |
|---|---|
| Default | Uses the matching repository or organization rule. Falls back to only me. |
| Only me | Requires your signed-in Sher account. |
| Anyone with the link | Opens for anyone who has the URL. |
For a session tied to a repository, the dashboard can also restrict access to people who can read that repository. Sher verifies repository access before serving the session.
An audience belongs to the session. An automatic sync rule supplies the starting audience for new sessions in its scope, but you can still make an individual choice when you share from the browser.
Keep a share live
The daemon follows session files that continue to grow:
sher daemon status
sher daemon startFor a single terminal and a single session, sher share --live stays attached until you press
Ctrl-C. The daemon is the normal choice because it follows every existing share and resumes after
you sign in to the machine.
Use sher status to see whether local records are still waiting to upload:
sher statusShare new sessions automatically
Create a rule for one repository or an entire organization:
sher sync on owner/repository
sher sync on organizationRules apply to new sessions by default. Include existing sessions explicitly:
sher sync on owner/repository --historyThe rule starts at only me until you choose another audience in the dashboard. The rule lives on your account, so every connected machine sees it.
To keep every new session on one device available only to you:
sher sync device onThe device rule is local and private. A repository or organization rule takes precedence for its own sessions.
Stop sharing
Open the share menu with s, choose unshare, and confirm it. From the command line:
sher unshareUnsharing deletes the remote share and makes the link stop working for everyone. It leaves the original agent transcript and Sher's local index in place. Sharing the same local session later creates a new link.
Turning off an automatic rule stops future sharing and leaves existing links in place:
sher sync off owner/repository