v0.3.0-beta.1 Public npm beta

Keep the work.
Change the thread.

A fresh coding session shouldn’t mean starting over. Carry the decisions, evidence and open work into your next thread—even in another agent.

npx @mahekara28/context-relay@beta ui

Public npm beta · Node 22.16+ · New thread map shown here is a development preview

Your workspaceLocal by default
Your next sessionContext, with sources
Context Relay · localhost0.4.0-dev.0 preview
Actual Context Relay thread map with a reviewed Claude Code to Codex connection and queued delivery, using synthetic sessions.
Drag between sessions. Review the context. Track delivery. Explore the new UI

Different harnesses.
One working context.

Claude Code
Codex
OpenCode
Goose
Explore integrations
01 / The context problem

The thread gets longer.
The next step gets harder.

Decisions get buried, corrections compete, and unfinished work disappears into a chat. Relay makes the state of the task explicit before you move on.

01

Start a fresh thread.

Select the events that matter and turn them into a focused checkpoint. Your next session begins with a goal and open work.

Review the source history
02

Carry the correction.

Keep current instructions beside the evidence they cite. When checkpoints disagree, choose the resolution explicitly.

See the review step
03

Switch the harness.

Offer the reviewed packet through MCP, or take a readable Markdown export. The destination can inspect the evidence before accepting.

Choose the next agent
02 / The local workspace

See the context.
Decide what comes next.

The new development dashboard discovers local threads, lets you connect them by dragging, and shows what was queued, sent and acknowledged. The public npm beta still ships the earlier workspace.

Context Relay · localhost workspaceView full size
Actual Context Relay thread map with four synthetic Claude Code, Codex, OpenCode and Goose sessions.

See indexed sessions from supported coding harnesses on one local canvas.

0.4.0-dev.0 preview · actual UI · synthetic sessions
03 / A deliberate handoff

From a long conversation
to a clear continuation.

A handoff carries the reviewed state of the work. Every checkpoint keeps references back to the history it came from.

  1. 01

    Discover

    Find local harness sessions and index completed turns in the background.

    Claude Code · Codex · OpenCode · Goose
  2. 02

    Connect

    Drag between thread cards, or use the card buttons, to choose a source and destination.

    Local thread map
  3. 03

    Review

    Check the source messages and write the goal before connecting.

    Evidence + destination + goal
  4. 04

    Deliver

    Queue an addressed handoff and see whether the receiver sent and acknowledged it.

    Queued → sent → acknowledged

Direct delivery needs a receiver: Claude MCP Channel opt-in, a reachable Codex host, or the existing OpenCode server. Goose and unavailable receivers retain the MCP or Markdown fallback. An agent acknowledgement does not prove task completion.

04 / Where MCP fits

One local service.
From threads to receivers.

Native adapters discover history. The graph holds reviewed connections; an outbox keeps delivery state until a receiver is ready.

Claude Code
Codex
OpenCode
Goose
Native history

Capture adapters

JSONL · app-server · local API · JSON export

Receiver path

MCP & native delivery

Claude Channel · Codex host · OpenCode API

Context Relay

Discover · Map · Review · Queue

CLI + local UI + MCP

Private SQLite workspace

Events, revisions, checkpoints and receipts.

Optional Nebius Token Factory

Selected evidence · validated draft · your review.

Capture reads native history. MCP alone does not expose a harness’s chat history.

Receiver requirements matter. Claude uses an opted-in MCP Channel, Codex needs a reachable host, and OpenCode needs its existing local server. Goose has a manual fallback.

05 / Bring your harness

Same project.
Your choice of agent.

Connections stay scoped to a local project. Relay preserves unrelated settings and removes only its own managed entry when you disconnect.

Claude Code

JSONL capture

Read project-matched transcripts. Add a project MCP connection and launch a fresh interactive continuation.

.mcp.json

Codex

App-server capture

Import completed turns through the native API. Continue from an addressed handoff in a fresh session.

.codex/config.toml

OpenCode

Local API capture

Read completed session messages from a loopback server. Use MCP or a portable Markdown packet.

opencode.json

Goose

CLI export capture

Import native JSON exports. Enable the generated stdio extension command to receive context through MCP.

.relay/goose-mcp.json

Connect your first harness.

Register your project, then use its returned ID.

relay project add --root /absolute/path/to/project
relay connect --project PROJECT_ID --harness claude
relay ui

Native formats can change. See the compatibility guide for source limits, OpenCode JSONC handling, Goose setup and Windows launch requirements.

06 / On your machine

Your context.
Your review.
Your call.

Local storage and manual handoffs work without an API key. You choose when source evidence goes to a model provider.

Read the workspace guide
01

A private local workspace

The service binds to 127.0.0.1. API access is authenticated, and the workspace stores its state in local SQLite.

02

Evidence you can inspect

Source references and recorded file hashes travel with the checkpoint. Recapture native sessions before relying on freshness.

03

Nebius when you ask for it

Preview the selected evidence, approve the request, then review the validated draft. Model output cannot create a checkpoint on its own.

04

Clear beta boundaries

Native integrations have protocol and fixture coverage. Live cross-harness task-quality evaluation is still pending.

Read the verification report
07 / Try it on your machine

A fresh thread starts here.

Install the public beta from npm, then open your local workspace. Node 22.16+ and npm are all you need.

v0.3.0-beta.1 · public npm beta

Install. Explore. Connect.

The package bundles the CLI, MCP server and local interface. No Python, frontend setup or model API key is required after installation.

  • 1Install the package from npm.
  • 2Explore the synthetic demo.
  • 3Connect a real project when ready.

Use @beta for beta updates, or pin @0.3.0-beta.1 for this exact release. View on npm.

Full installation guide Release notes
terminal / macOS · Linux · PowerShell
npm install --global @mahekara28/context-relay@beta
relay demo
relay ui
Opens your own local workspace.

Already installed?

Open your workspace or inspect its service.

relay ui
relay status
08 / Go a little deeper

Built in the open.

Inspect the format, understand an adapter, or help improve the next release.

A few useful answers

Before you relay.

Is this a hosted workspace?

This website introduces the project. Your actual workspace runs locally through relay ui. The website does not connect to your local service, collect conversations or run terminal commands.

Does it copy my entire conversation into a new agent?

You select source evidence and review a focused checkpoint containing the goal, current instructions, acceptance criteria and open work. Packets have a byte budget and disclose omitted evidence. Hidden model state is not transferred.

What is the difference between capture and MCP?

Capture adapters read a harness’s native history when requested. MCP lets a destination agent inspect Relay’s sources, retrieve a packet and accept an addressed handoff. Both use the same local service.

Do I need a Nebius API key?

No. Manual checkpoints and handoffs are keyless. Optional Nebius drafts require a configured key and model, an evidence preview, explicit consent, and your review of the result.

Does accepting a handoff mean the task is done?

No. Acceptance records delivery after checking the recipient, packet integrity, captured revisions and recorded file state. The receiving agent still needs to do the work and verify its results.

What does the beta support today?

A local npm CLI and workspace, four capture adapters, MCP access, checkpoint review and merging, handoff receipts, Markdown export, and interactive Claude Code/Codex launch. Install the public npm beta globally or run it with npx. Live model-quality evaluation remains pending.

Continue with context

Start fresh.
Bring what matters.

Try the betaExplore on GitHub

Copy this command

Your browser could not access the clipboard. Select the text below.