ResumeContext

What it is

ResumeContext is a shared project archive for coding-agent sessions. We verified resumecontext.com on 2026-09-23 (HTTP 200): a small CLI/daemon syncs the session history that Claude Code, Codex, Cursor, and similar agents already write to disk into one archive per project, then every agent on that project can search it back over MCP. Team context stops living only on someone’s laptop; when one agent hits a usage limit, you open another tool or account pointed at the same project and pick up mid-task with citations to the prior session and line.

Setup is intentionally thin: install the CLI, sign in, run resumecontext init in the project directory, then connect your agent to the MCP server. The site says sync runs about every twenty seconds on machines that are on; the in-progress session you are in right now is the main lag. Access is per project directory — teammates invited to one repo do not see your other projects. Storage includes prompts, replies, and tool calls with their outputs, so source the agent read or wrote can land in the archive; treat that as a privacy boundary, not a side effect.

Who it’s for

Small teams and solo makers who already live in coding agents and keep losing context across machines, accounts, or usage-limit walls. If you never parallelize agents and never hand work between people, a personal transcript is enough. If managers or teammates keep asking “what moved?” and the answer is buried in someone else’s agent log, a project-scoped searchable archive is the interesting shape.

Why we listed it

Fresh public launch: Product Hunt featured day 2026-09-22, live site verified 2026-09-23. Category gap on this board — we list agent runtimes, firewalls, and Mac leftovers, but not a team-shared MCP memory layer for existing agent transcripts. Fits the new-only bar: early indie beta (free while beta, no card), not a household knowledge-base brand.

Caveats

We have not installed the daemon on ops machines or audited what leaves the laptop. Beta pricing will change; claims about agents supported and sync latency are vendor statements. Anything your agent puts in a tool call (including code and secrets) can enter the archive — scope projects carefully and revoke leavers. Windows is described as working except background sync; treat cross-platform behavior as something to verify yourself.