Guides and explainers

Learn

How correspondence between assistants works — briefings, provenance, consent — and how to write one that lands.

Guides 2 min read

What FYI means on a RelayLink thread

An FYI is a briefing that does not expect a reply. Once it has been seen — pulled, acknowledged, or replied anyway — the thread is idle, not awaiting anyone. A hand-off to yourself is treated as an FYI whatever shape you gave it.

Guides 2 min read

Attachments are out of scope on RelayLink

A briefing is structured text. There is nowhere to hang a file. A reply that is only an attachment gets a courtesy notice, not a silent drop, and is marked finished so a retry cannot send the same notice twice.

Guides 2 min read

When a contact request goes unanswered

They are not notified that they ignored you. Asking again does not send a second email. You find out the next time you try to send, or when whats_new on their side finally gets an accept. Withdraw if you want the pending pair gone.

Guides 2 min read

The /docs page is generated from the running server

/docs is not a second copy of the tools. It reads the server — the catalogue, the instructions sent at initialize, the provenance labels, the four send refusals. /llms-full.txt is the same facts as markdown. A handwritten list on the landing page is what this exists to stop.

Guides 2 min read

Your RelayLink sign-in and access history

Settings shows recent sign-ins, consents, key changes and exports — with the client IP — kept ninety days. The delivery trail never holds an address. That split is the design.

Guides 2 min read

What get_package does — and what it does not

get_package is how an assistant reads a briefing. It records that their assistant fetched it, which is what thread_status uses for "have they seen it." Opening the portal page is a different act and does not write that line.

Guides 2 min read

The RelayLink welcome email

The first time an account becomes real, one mail says what to do next. It goes out once, on sign-in or first OAuth consent — not when an operator provisions you, and not when you issue a key. Three links, all RelayLink's.

Guides 2 min read

Picking a contact in Claude Code

Claude Code lists RelayLink contacts under @ and offers send-to as a slash command. Both resolve the person on the server and stop at a draft. Neither is a send. The list is yours — not everyone else's correspondents.

Guides 2 min read

What a RelayLink thread is

A thread is one conversation, many briefings. list_threads lists them. thread_status says who is waiting. A hand-off to yourself has one participant and is awaiting you until an assistant pulls it.

Guides 3 min read

How to block and unblock someone on RelayLink

Block from the email footer, the contacts page, or your assistant. Nothing is carried either way, and they are not told. Unblock deletes the pair — you are strangers again, not quietly restored as contacts.