One project.
A complete round trip.

01 / CONTEXT

Start with the fictional project.

In an empty Studio, choose Try a fictional project. Open Fictional community project. You will see two approved example facts, a budget note awaiting review and a separate space with another draft.

Project scope

This fictional project is a neighborhood book exchange with a simple online catalog.

Writing preference

Use plain language and short paragraphs in the project plan.

Source

Fictional planning note

If you entered these yourself, choose Save for review, inspect the wording in Context and approve the facts. Approval records your review; it does not independently verify the source.

BRING EXISTING WORK

Choose useful parts of a project note.

For your own project, open a space and choose Import a note in Context. You can work from a README, decision note or a summary you deliberately saved from an assistant.

1. Use Paste a note and choose Review excerpts, or Choose a .txt or .md file to inspect its excerpts. Processing stays in this browser.
2. Choose the paragraphs or list items you want. Nothing is selected for you. To take a smaller part, select it in the original note and choose Add selected text to review.
3. Compare each original excerpt with its editable draft. Give it a useful label, choose its kind and check the wording and source. Long excerpts need an explicit edit before keeping; nothing is silently trimmed.
4. Choose Keep selected drafts, then Review drafts. Keeping a draft does not approve or share it. Inspect the saved wording in Context before approval and handoff selection.

02 / PREPARE HANDOFF

Give the next conversation a clear starting point.

1. Open Prepare handoff. Choose an assistant label, such as Claude. This labels your snapshot; it does not connect an account.
2. Select Project scope and Writing preference. The draft budget and the other space are excluded.
3. In What should it do next?, enter the example objective below.
4. Choose Prepare exact snapshot, then expand Inspect complete AI handoff text. Review the objective, selected facts and guidance together.
5. Choose Copy for Claude or Download. Open a new conversation in your assistant and paste the complete handoff. If clipboard access fails, download the Markdown file and copy its contents.

Prepare a short implementation plan for this fictional book exchange. State the open questions before the plan. Do not invent a budget, deadline or confirmed technical decisions.

The handoff includes a format for proposed updates. Read the assistant’s answer yourself: a prompt can ask it to preserve uncertainty, but cannot guarantee that it will.

Manual paste transfers the text you chose into the receiving service. Its data controls apply there. Selfrelay cannot recall that copy afterward.

03 / REVIEW UPDATES

Return with a proposal, then make the decision.

For a practice correction, suppose the project will start with an in-person catalog. The JSON below is a fictional proposal you can paste yourself; generating it with an assistant is optional.

{
  "proposals": [
    {
      "kind": "project",
      "label": "Project scope",
      "value": "This fictional project is a neighborhood book exchange. Start with an in-person catalog; an online catalog is a later proposal.",
      "sourceLabel": "Fictional planning revision for this exercise"
    }
  ]
}

1. Open Review updates. Set Input format to Assistant response or proposal JSON, paste the proposal into Selected assistant response and choose Preview proposals.
2. Under Keep as, select Correction to: Project scope. Compare it with the current wording, then choose Keep for review.
3. Open History and choose Review changes & update on the earlier snapshot. Compare In the saved snapshot with In this workspace now, including the wording and source. The saved snapshot keeps its original text.
4. The correction is still a draft. If its wording and source are ready, choose Approve this wording and source. Then explicitly choose Include the current approved version or Leave this fact out for every changed fact. For a removed fact, explicitly choose to leave it out. Approval alone does not select a correction for sharing.
5. Review the title, assistant label and next objective, then choose Prepare reviewed replacement. Choose Inspect selected replacement, then expand Inspect complete AI handoff text, review the full text, then deliberately copy or download it. If you want hosted access, sign in and separately choose Publish selected snapshot after reviewing its selection and duration.
6. In Review old and replacement access, choose Refresh access. Sign in if prompted, then refresh again. Review the grants that exactly match each snapshot and the linked assistant statuses. To retire an old grant, use its Revoke old access for… button and check the confirmation.

You can also paste a whole assistant response containing one JSON proposal block. If it has several blocks, copy only the intended proposal JSON. {"proposals": []} means no changes were proposed.

04 / SAVE & RESTORE

Choose how you keep your workspace.

Open Save & restore before leaving. These are separate options, so choose the one that fits the material you are keeping.

Save on this device

Retains a readable copy in this browser. It is not encrypted. Sign-out does not clear it.

Download JSON backup

Downloads a readable workspace file you can restore later. Keep the file private. A downloaded handoff contains only its snapshot and is not a full workspace backup.

Encrypted cloud backup

Requires Selfrelay sign-in and a passphrase. Encryption happens in the browser before saving. Backup and restore are manual, and a forgotten passphrase cannot be recovered.

Cloud backups and published snapshots are different: publishing uploads a readable selection that token holders can request. The encrypted backup does not silently update your other devices or AI conversations.

If you sign in while keeping device saving off, follow the download and acknowledgement step, then restore the downloaded workspace after returning. Finish or cancel unfinished inputs first.

OPTIONAL / LIVE ACCESS

Let a compatible tool read a selected snapshot.

The manual handoff above needs no connector. To use a manually configured API or MCP bearer token, sign in to Selfrelay, prepare and inspect a current snapshot, then expand Use a temporary API / MCP grant instead.

1. Choose a duration, acknowledge the selection and choose Publish selected snapshot.
2. Store the displayed token privately. It is shown only in the current tab and is not included in your backup.
3. For Codex CLI or Claude Code, use Connect this snapshot beside the displayed token. Download the launcher and follow its terminal steps. Your assistant must already be installed and signed in. Paste the token only into the hidden launcher prompt.
4. Copy the first prompt from Studio into your coding assistant. It asks the assistant to call read_approved_context for that snapshot and state its selected facts, objective and unknowns. A successful launcher check alone does not prove a tool call.
5. Check the retrieved facts. Revoke the grant in Live access when the task is done or its facts change.

Anyone holding the token can read that snapshot until expiry or revocation. The assistant label does not bind the token to a particular app. Custom bearer-header support varies by client.

The coding-agent launcher does not edit global configuration or include your token in the downloaded file. Node.js 22 or later is required. It keeps the token in the assistant process environment for the session. This direct MCP setup is separate from the hosted Claude connector and uses no hosted connector slot. Other compatible clients can use the endpoint and bearer header described in the developer guide.

Selfrelay also has an experimental OAuth flow for hosted Claude; follow the supported setup instructions below. It asks you to sign in and select one published snapshot on a consent screen, then issues separate access credentials for that selection. Your Selfrelay sign-in tokens are not given to the assistant.

Setup requires an available custom-connector slot. An end-to-end connection inside Claude has not yet been verified. This experimental flow does not support Claude Code’s native callback or automatic client registration. Manual handoffs and compatible bearer-token clients remain separate options.

BETA EVIDENCE / 8 SEPTEMBER 2026

What we have actually exercised.

Codex through MCP

One public-domain Codex CLI invocation returned exactly one selected fictional fact and treated missing facts as unknown. After revocation, another MCP request was denied. This verifies that path and case, not every Codex setup or a general reliability rate.

Claude through manual paste

A fictional initial handoff and correction preserved the supplied facts and unknowns. The initial answer placed uncertainty after its plan. One focused retest with revised guidance put uncertainty first and returned an importable empty proposal list. These were manual-paste trials; they do not verify the experimental hosted Claude OAuth connection.

Comparison with Markdown

Selfrelay and carefully curated Markdown both preserved the selected content in 100 deterministic fictional cases. That check did not measure human effort or establish a comparative winner. Review and correction controls are the product proposition to evaluate in your own workflow.

Selfrelay remains an early beta. There is no automatic AI history sync, independently verified identity or guarantee that an assistant will follow the handoff. The software has not had an independent security audit.