Context that carries yourwork forward.

Thread gives Claude, Codex, and Cursor shared memory for decisions, revisions, and unfinished work, so the next agent starts where the last one stopped.

One shared memory, available through MCP wherever your agents work.

Claude

Codex

Cursor

Windsurf

Cline

MCP

One memory for every agent that touches the work.

Claude saves the decision and the next step. Thread resolves what changed. Codex continues with the context it needs.

Connect an agent

Keep the work connected across every handoff.

Thread keeps the active task, changing decisions, and supporting evidence available to the next tool that needs it.

Start every agent with context

Copy the instructions for the agent you use, then let Thred carry the decisions and next step forward.

Resume a handoff

Every saved checkpoint is ready for the next agent to pick up without losing the work in motion.

Connect Thred through MCP

Use your real MCP configuration to bring shared workspace memory into the tools your agents already use.

Said on X

Builders are already handing work off.

What people said when Thred shipped. Unedited, straight from the replies.

Harnoor Singh

@iHarnoorSingh

this is lit!! better memory and reduces the need of openrouter

Aug 18, 2026

waishnav

@wshxnv

good work :) at some point i was gonna build smth similar the context layer for codebases but aparently models got better at exploring codebases on demand, so dropped that idea you should do eval/benchmark btw

Aug 18, 2026