Works with Claude · ChatGPT · any MCP client

Hand context from
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 How it works
Claude ChatGPT Cursor 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.

✗ 01

Re-explaining

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

✗ 02

Copy-paste

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

✗ 03

Vendor 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.

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

STEP_01

Save it

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

STEP_02

Pass the handle

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

STEP_03

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

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

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

Brief every new AI once

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

Sharing · Segue Pro

Hand a context to someone else

Same handle, same context — pointed at a person instead of another one of your assistants. Read-only, time-limited, and revocable in one click.

One link

Send it by email

Share a saved context with one person by address. They get the title and a link — never the contents in the email itself — and you get a log of when it was opened.

No account needed

They can just read it

Someone without Segue reads a snapshot in the browser or downloads the Markdown. If they do have an account, they get the live context and can load your handle in their own AI.

Still yours

Expires and revokes

Every share carries an expiry — 14 days by default — and revoking kills the link on the next request. Nobody can edit what you shared, or pass it on.

✓

Sending is Pro; receiving is free, always. Reading a context someone shared with you is never paywalled and never needs an account — on any plan, in any state. And if a subscription lapses, every share already sent keeps working; only new ones pause.

Principles

Deliberate by design

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

Explicit

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

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

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

Yours unless you say otherwise

A handle resolves inside your account — and nowhere else, unless you deliberately share it with one named person. Guessed or leaked, it stays meaningless.

Portable

Plain Markdown

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

Revocable

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
$0
  • 20 saved contexts
  • 2 connected AIs
  • Save, load, and search — the full loop
  • Projects, web editor, Markdown export
  • Read anything shared with you
Start free
Pro
$5 /month — or $48/year
  • 2,000 saved contexts
  • Unlimited connected AIs
  • Share contexts with other people
  • 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?

Three pronounceable syllables — like brelavo — minted when a context is saved. It's the context's address: case-insensitive, unique, and resolvable inside your account — plus, if you choose to share it, for the one person you sent it to.

Which AIs work with Segue?

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?

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?

Only if you shared it with them on purpose. Otherwise no — handles resolve only for clients signed in to your account, and outside it a handle is just a made-up word. A share goes to one address you name, is read-only, and can be revoked whenever you like.

Does Segue read or auto-capture my conversations?

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?

Your account drops to the free tier. Everything already saved stays loadable, editable, exportable, and deletable — only new saves pause while you're over the free cap. Shares you've already sent keep working too, and you keep the controls to revoke them; only sending new ones pauses.

Can I share with someone who doesn't use Segue?

Yes. They open a link and read it in the browser, or download the Markdown — no account, no payment, nothing to install. If they'd rather have it in their own AI, creating a free account on that address turns the copy into the live context, loadable by handle. Sending shares needs Pro; receiving one never does.

Stop re-explaining yourself

Create a free account, connect your AI over MCP, and start handing off context.

Start for free