# ResumeContext ResumeContext é um serviço de memória compartilhada para equipes de agentes de programação. Registra sessões localmente, sincroniza-as com um arquivo do projeto e o disponibiliza aos agentes por meio do MCP, para que possam pesquisar trabalhos anteriores e continuar entre agentes, contas ou máquinas. - Findings24: - Site: - Preços: Freemium - Categorias: Ferramentas Dev IA ## O que é ResumeContext? ResumeContext is a shared memory service for coding-agent teams. A local daemon reads the session history that supported coding agents already write to disk, syncs those sessions to a shared project archive, and makes the archive available to agents through the Model Context Protocol (MCP). The product is designed to preserve project decisions, investigations, and unfinished work beyond an individual agent session. Its main workflows are cross-agent continuity and shared team recall. An agent can search previous sessions and return answers with references to the originating session and line. Because the archive is associated with a project rather than a particular agent or account, a developer can switch tools, accounts, or machines without starting the task context over. ## O que ResumeContext pode fazer? ### Shared project archive Sessions from team members are collected in one archive associated with a project, allowing agents to access prior project work. ### MCP access for coding agents The archive is provided back to coding agents as an MCP server, so users can query shared history from the agent session they are already using. ### Cited historical answers Responses can identify the source session and relevant line range, making it possible to trace an answer back to the recorded work. ### Automatic local syncing A small daemon reads agent history from local disk and syncs it without requiring an installation inside the agent or changes to prompting. ### Agent and history selection The \`resumecontext agents\` command can list supported agents, inspect their history locations, and choose which agent histories to sync, including custom paths. ### Searchable long-term context Months of sessions remain searchable, with the agent retrieving relevant passages instead of requiring all history to remain in the active context window. ## Casos de uso ### Continue after an agent usage limit Point another agent at the same project archive when the current tool reaches its limit, allowing work to continue without manually reconstructing the previous session. ### Share debugging findings A teammate can ask what another developer discovered about a bug and receive an answer grounded in the recorded investigation, including session and line references. ### Coordinate project work Project members can ask what changed, who is blocked, or whether work is overlapping, using the team’s recorded sessions instead of separate status updates. ### Switch development environments The project archive supports continuity when work moves between agents, accounts, or machines, provided those environments are connected to the same project. ## Perguntas frequentes ### Which coding agents does ResumeContext support? The product reads session history from supported coding agents. Its agent-management command can list supported agents, show their normal history directories, report whether history is present locally, and configure a custom history path where needed. The supplied documentation examples include Claude Code, Cursor, and Codex, but the complete supported-agent list should be checked in the current documentation. ### Does ResumeContext require an agent plugin? No. ResumeContext reads the history agents already write to disk and returns the shared archive through MCP. The documentation states that nothing is installed into the agent and prompting does not need to change. ### How is the product set up? The quickstart describes a setup of about two minutes: install the CLI, sign in, run \`resumecontext init\` in the project directory, and connect the coding agent. After setup, it syncs automatically. The setup is performed on each machine that will contribute or read project history. ### Where is conversation history stored and who can read it? History is stored on ResumeContext’s servers within the project it was synced to and is readable by members of that project. The pricing page states that agent access is read-only and enforced by a database role without access to other data. ### What happens when a teammate is removed? A teammate can be removed from the project page, and their access ends immediately. Sessions they already recorded remain in the archive and retain attribution to that teammate. ## Informações rápidas - **Category**: Developer Tool - **Primary users**: Teams using coding agents - **Core protocol**: Model Context Protocol (MCP) - **Setup**: CLI, sign-in, project initialization, and agent connection - **Beta pricing**: Free during beta; no card, trial countdown, or stated usage limits - **Team access**: Project members can be invited by email