How to share your coding agents read-only with your team
Run peerband share without --message. The person who accepts can list your machine's agents and read their status and recent output, but can't message them. Revoke access at any time.
Create a read-only invite
peerband shareRead only is the default. The link works once and expires after 7 days, or set --expires DAYS.
What a read-only guest can do
- See your machine and its agents in their dashboard, with live status.
- Ask their MCP client "What is the agent on Alex's machine working on?". The client can call
list_agents,get_agent_status,get_agent_outputandwait_for_agent. - Nothing else:
send_agent_messagefails for them, and they don't get your notes or webhooks.
Good uses
- Pairing: a teammate follows along while your agent works on a shared branch.
- Standups: a lead checks what each agent finished without asking.
- Handoff: someone in another time zone checks whether the overnight run is done.
Recent output can contain anything your agent printed. Before sharing, make sure the agents on that machine don't print secrets, or limit what's visible with allowedAgents and allowedWorkspaces in connector.json.
Manage access
peerband share list shows who has access and unused links. peerband share revoke ID removes a person (IDs starting acc_) or cancels a link (inv_). In the dashboard, the same is under People with access and Unused links.
Questions
Can I upgrade someone to send messages later?
Yes. In the dashboard, change their access from Read only to Read + message.
Is output redacted for guests?
Output is limited to a bounded recent excerpt, and likely secrets are redacted as a best effort. Treat it like screen sharing.