Ever lost your place when a Claude chat gets too long? Relay carries the full context of one chat into a fresh one — in a single paste.
Relay reads your current Claude conversation and writes one portable briefing you paste into a new chat to continue exactly where you left off. No re-explaining, no lost decisions, no context bloat slowing every reply.
Also known as: Claude context handoff · session handover · continue a Claude chat in a new conversation · transfer context between chats · save chat context.
Long chats degrade — context fills, tokens burn, answers get less sharp. Anthropic suggests keeping chats short for this reason, but real work runs long. Relay lets you split work across fresh chats without losing the thread.
Most handoff tools are built for Claude Code repos (git scaffolds, file storage, staleness-vs-commits). Relay is built for chats:
- Chat-native — pure copy-paste output; no repo, git, or CLI required.
- Domain-adaptive — detects whether you're doing coding, design, writing, research, analysis, marketing, or strategy, and captures what matters for each.
- Purpose-tailored — tell it what the next chat is for and it aims the briefing.
- Settled vs. still-open split — separates locked decisions from open threads so the next chat never re-litigates or redoes work.
- Self-check quality gate — verifies no hollow sections and redacts secrets before output.
- Chain-aware — relays link across 3+ hops without losing history.
- Claude apps (web/desktop/mobile): Settings → Capabilities/Skills → upload
this
relayfolder (or the zip). (Custom skills require a paid plan.) - Claude Code / API: drop the
relay/folder into~/.claude/skills/relay/.
Say "relay" — or any natural equivalent: "handover", "hand off", "carry this over", "this chat is getting long", "continue in a new chat", "pass the baton". Optionally add a focus: "relay — the next chat is just the dev build".
Claude prints a copy-paste briefing block (and saves a .md when a file tool is
available). Open a new chat, paste it as your first message, and continue.
See EXAMPLE.md for a filled-in briefing.
Relay follows Semantic Versioning: major = breaking
change to the briefing format · minor = new capability · patch = fixes and
wording. The current version is in SKILL.md (front-matter) and every change is
logged in CHANGELOG.md. Each release is a git tag (vX.Y.Z) with
notes and a downloadable zip on the GitHub Releases page.
Maintainer note: when releasing, bump version: in SKILL.md and add a
CHANGELOG.md entry — keep them in sync.
Trigger it at ~50–75% context — before answers lose sharpness, not after.
Repo: github.com/mosuvo/relay · Built by Mo Suvo — @mosuvo · github.com/mosuvo.
MIT licensed. If Relay saves you from re-explaining a chat, a ★ on GitHub or a share is appreciated. Issues and improvements welcome.