beacon share publishes one local agent session as a shared trace on beacon.sh and prints its link. It reads the session from your own machine, so it works for any runtime Beacon captures, whether or not the endpoint is connected to Beacon Cloud.
Sign in
beacon login opens a browser to sign in to beacon.sh. The sign-in carries the traces:write permission beacon share needs. On a machine without a browser, use an API key instead.
Share a session
Runbeacon share in the directory where the agent worked:
Example output
--harness matters when more than one runtime worked in the same directory. See Choosing the session for every selector.
Check before you share
--print shows exactly the payload that would be uploaded, as JSON, and sends nothing:
Set visibility and title
Without a terminal,
--visibility public is refused unless you add --yes. A re-share keeps the trace’s visibility unless you pass --visibility again.
Keep a trace up to date
Sharing a session again updates the same trace; nothing is duplicated. Two commands keep it current:--follow checks the session locally every interval (default 10s) and makes a request only when something changed. It stops when the session records its end.
Script it
--json prints one document, for scripts and agents:
{"ok":false,"error":"..."} and exits non-zero.
See what you shared
After an upload,beacon share records a session.shared event in the local runtime log with the link and visibility, so the local dashboard and beacon endpoint traces list --state shared mark the session as shared. A shared session with newer local activity shows as stale, with the beacon share refresh command to bring it up to date.
Related
beacon share reference
Every flag, how
--current finds a session, and the upload format.Sharing via Agent Skills
Let your agent run
beacon share for you.