> ## Documentation Index
> Fetch the complete documentation index at: https://resumecontext.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# ResumeContext

> Make coding agents multiplayer. One shared archive of every session, handed back to every agent on the team through MCP.

## The problem

A coding agent starts every session blank, and every session it records dies on
the laptop that made it. The decisions you argued out yesterday, the approach a
teammate already rejected and why, the value someone settled on after three
attempts. All of it is in a transcript nobody else can search.

So each person re-explains the same project to the same kind of agent, every
day, in parallel.

## What ResumeContext does

A small daemon records your coding-agent sessions locally and syncs them to a
**shared project archive**. Every agent on the team then gets that archive back
as an **MCP server**, and answers from your real history inside the session you
are already in.

It reads the history your agents already write to disk, so nothing is installed
into the agent and nothing changes about how you prompt. See
[`agents`](/docs/cli/agents) for the ones it reads today.

## What it is for

Two things, and they are the reason to install it.

<Card title="Your team stops re-deriving what someone already worked out" icon="users">
  Everyone on a project pushes to the same archive. When you start a session,
  your agent can read what a teammate did this morning: the approach they took,
  what they ruled out, and why. `what did Priya change in the auth flow` is
  answered from her sessions, cited by session and line, rather than from a
  stand-up you both had to attend.
</Card>

<Card title="A usage limit stops the agent, not the work" icon="right-left">
  The archive is a plain MCP server, tied to the project rather than to an agent
  or an account. When one agent hits its limit, point the next one at the same
  project and it reads everything the last one did. A different tool, a second
  account and a different machine all work the same way.
</Card>

## What else it gets you

<CardGroup cols={2}>
  <Card title="Managing a team without the status round" icon="chart-line">
    Anyone with access can ask the project what moved this week, who is stuck
    and on what, and whether two people are quietly solving the same problem.
    Answered from the sessions the work happened in, so nobody writes an update.
  </Card>

  <Card title="Recall past any context window" icon="clock-rotate-left">
    Months of sessions stay searchable. The agent pulls in only the passages
    that matter, rather than holding history in the window to keep it.
  </Card>
</CardGroup>

<Note>
  ResumeContext is free to use while it is in beta.
</Note>

## Start here

<Card title="Quickstart" icon="rocket" href="/docs/quickstart">
  Four commands, about two minutes. After that it syncs on its own.
</Card>