Segue — hand context from one AI to the next

Works with Claude · ChatGPT · any MCP client

Hand context from<br>one AI to the next.

Save a block of context in one assistant and get a short handle back. Load it by that handle in another — no copy-paste, no re-explaining. Your context, carried across tools.

Start free<br>How it works

Claude<br>ChatGPT<br>Cursor<br>Any MCP client

The problem

Every AI keeps your work in its own silo

You plan in one assistant, build in another, and draft in a third. Each one holds real working state — the brief, the constraints, the decisions so far. None of them will hand it to the next.

So the state of your work gets rebuilt from memory, every time you switch tools. That tax is small enough to pay once and large enough to feel every day.

✗ 01Re-explaining

Retype the background in every new tool, losing fidelity each time.

✗ 02Copy-paste

Haul transcripts between windows. Clumsy on a desktop, hopeless on a phone.

✗ 03Vendor memory

Each assistant remembers — for itself. It can't brief a competitor's tool.

How it works

Three steps, one handle

Connect any MCP-capable AI to Segue over OAuth — then let it carry context for you.

Claudeplanning

save this plan for my coding agent

save_context(…)

Saved — the handle is brelavo.

──▶<br>brelavo<br>you carry it

Cursorbuilding

load brelavo from Segue

load_context("brelavo")

Loaded. Picking up where you left off

Handles are three pronounceable syllables. Say one aloud, type it on a phone, write it on a sticky note.

STEP_01<br>Save it

One AI calls save_context with your working brief, notes, or plan — and gets back a short handle like brelavo.

STEP_02<br>Pass the handle

Hand that handle to another assistant — anything connected to the same Segue account.

STEP_03<br>Load it

The next AI calls load_context with the handle and picks up exactly where you left off.

Where it fits

Made for the way you already work

Across tools<br>Plan here, build there

Think in Claude, implement in Cursor, draft in ChatGPT — and carry the brief between them instead of rebuilding it.

Across sessions<br>End today, resume tomorrow

Hitting a context limit or closing for the night? Save a curated brief instead of dragging a sprawling transcript forward.

Standing briefs<br>Brief every new AI once

Keep project background, house style, and preferences saved — and bootstrap any newly connected assistant on demand.

Principles

Deliberate by design

Segue is a small, neutral relay between your AIs — built on commitments, not features.

Explicit<br>You carry the baton

Nothing syncs behind your back. An AI saves, you pass the handle, another AI loads. Every transfer is one you chose.

Human-scale<br>Handles, not URLs

The unit of exchange is a word you can say aloud or type from memory — even when the context behind it runs to 100,000 characters.

Neutral<br>No vendor's ground

Segue belongs to no assistant. Any MCP-compliant client connects the same way — today's and whatever you switch to next.

Private<br>Yours alone

A handle resolves only inside your account. Leaked or guessed, it's meaningless to anyone else — by construction.

Portable<br>Plain Markdown

Every context is readable text you can browse, edit, search, and download as a .md file. No lock-in format.

Revocable<br>Narrow, short-lived access

Each AI gets scoped permissions and short-lived tokens, listed in Settings with one-click revoke. Stored credentials are hashed.

Pricing

Free to relay, Pro for headroom

Free<br>$0

20 saved contexts

2 connected AIs

Save, load, and search — the full loop

Projects, web editor, Markdown export

Start free

Pro<br>$5 /month — or $48/year

2,000 saved contexts

Unlimited connected AIs

Everything in Free

First access to new features

Go Pro

Your data is never hostage. Loading, editing, exporting, and deleting stay free on every plan, in every state — lapsed ones included. Paying buys headroom, never access to your own words.

FAQ

Fair questions

What exactly is a handle?<br>Three pronounceable syllables — like brelavo — minted when a context is saved. It's the context's address: case-insensitive, unique, and resolvable only inside your account.

Which AIs work with Segue?<br>Any client that speaks MCP with streamable HTTP and OAuth — Claude (Desktop, Code), ChatGPT, Cursor, Windsurf, Codex, and more as the ecosystem grows. Setup is pasting one prompt: the AI configures itself and walks you through sign-in.

What is MCP?<br>The Model Context Protocol — an open standard, stewarded by the Linux Foundation, that lets AI assistants connect to outside tools. Segue is one server that all your assistants share.

Could someone else load my handle?<br>No. Handles only resolve for clients signed in to your account. Outside it, a handle is just a made-up word.

Does Segue read or auto-capture my conversations?<br>Never. Nothing is saved unless an AI you connected calls save_context in front of you, and nothing loads unless you pass the handle. No ambient memory, no surprises.

What happens if I stop paying?<br>Your...