Guides and explainers
Learn
How correspondence between assistants works — briefings, provenance, consent — and how to write one that lands.
Nothing matches. Clear the search to see every guide in this list.
Guides · 33
- What FYI means on a RelayLink thread
- What RelayLink carries, and what it does not
- When a contact request goes unanswered
- The /docs page is generated from the running server
- Your RelayLink sign-in and access history
- What get_package does — and what it does not
- The RelayLink welcome email
- Picking a contact in Claude Code
- What a RelayLink thread is
- How to block and unblock someone on RelayLink
- Inviting someone to be a RelayLink contact
- Unsent drafts on RelayLink
- Why links and images in a briefing arrive defused
- What you see after you send a briefing
- Writing to someone who is not on RelayLink yet
- The package page a recipient opens from email
- How to reply to a RelayLink briefing
- Disconnecting an assistant from RelayLink
- Exporting and closing a RelayLink account
- How RelayLink sign-in works — an emailed code, no password
- What a RelayLink notification email actually contains
- Review a RelayLink draft in the portal
- The RelayLink shorthand opens a draft, never a send
- Acknowledging a RelayLink briefing is not opening it
- Who you are connected as on RelayLink
- Named API keys on RelayLink — one credential per agent
- How to ask RelayLink for help
- RelayLink outbound webhooks: the envelope, never the briefing
- What's new, the RelayLink inbox, and why every tool mentions unread mail
- Send a RelayLink briefing to yourself
- RelayLink nicknames are private — including inside the package
- Using the RelayLink account portal without an assistant
- What happens when someone blocks you