Keep every project moving.

SharedContext keeps each project's decisions and current state in one place your Agents read — so every session picks up where the last one stopped.

Connect your Agent How SharedContext works

Works with Claude, ChatGPT, and any MCP-enabled Agent

SharedContext in motion

Projects stay separate.
Work carries forward.

Each project keeps its own Context. Agents working in the same project start from it — other projects stay out of reach.

Planning Agent

ChatGPT

recording confirmed scope

Interface Agent

Claude Code

Build the pricing experience

Systems Agent

Codex

Wire usage metering

Research Agent

MCP client

Synthesize team signals

SharedContext project scoped

space / projects / launchrevision 4

briefs/launch.md

decisions/launch-scope.md

work/interface.md

work/metering.md

research/teams.md

releases/v1.md

user-confirmed scope recorded

01 / Capture

A confirmed decision stops being chat history.

When the user confirms the launch scope, the Agent saves that decision to the project. Proposals and open questions stay marked as undecided.

02 / Read

Different Agents share a starting point.

Agents working on interface, systems, and research open the same project index. Context from other projects never leaks in.

03 / Update

What one Agent learns, the next one can use.

The research Agent saves what it learned as a finding, not a decision. The next Agent can build on it without mistaking it for something the user approved.

04 / Carry forward

The next session begins further ahead.

Confirmed decisions, findings, and implementation state remain in the project. The next Agent can continue without reconstructing the briefing from scratch.

SharedContext

Run more projects without carrying them all in your head.

SharedContext does the enforcing: Context stays inside its project, every Agent knows how to re-enter, and your decisions stay apart from what Agents propose.

01Scope

Keep each project distinct.

Agents share Context inside a project — and only there. Space-wide conventions still apply everywhere, but each project's Context stays its own.

02Handoff

Give every Agent a way back in.

Every session starts by confirming which project it is in. From there, indexes and search lead the Agent to the current state — whichever tool or branch the work happened in.

03Carry forward

Decisions stay yours. Work compounds.

User-confirmed direction stays separate from proposals and findings, and revision history preserves how the Context changed — a guess never quietly becomes the plan.