AGENT CONTEXT / DOCS
Keep your agents on the same page.
Start a local instance, connect your coding tools, and make every handoff useful.
Download, install, and open the local dashboard.
Connect your coding agents.Use the same project ID and database across clients.
Choose your agent, system, and model.Understand MCP requirements, local models, shared connections, and what has been verified.
One team. One shared context.Connect over the same Wi-Fi, a private VPN, an SSH tunnel, or an HTTPS server.
Run it on your terms.Understand credentials, storage, backups, and the instance trust boundary.
Get back to building.Resolve installation paths, tokens, network errors, client setup, and website deployment.
Build it with us.Read the source, run the checks, and propose focused improvements.
Start here
Install the downloadable package or build from source with the quick start. Then choose a client and verify a handoff. For several computers, use the team guide. The active product is Node.js/React; Python setup is historical.
The public npm registry release is pending until verified by the maintainer. Downloadable artifacts are built from this source; a website build alone does not prove public deployment or passed cross-platform CI.
What Agent Context does
It keeps structured project context available through MCP. One agent records the work; another reads the handoff before continuing. The dashboard and coding agents use the same database.
The core loop
- Read project context and current tasks.
- Claim the next task using its current version.
- Inspect the repository, implement, and verify changes.
- Record meaningful updates and leave a useful handoff.
Recorded context, with evidence
The server stores the facts agents report. It does not automatically capture chat history, execute tests, or validate file changes. Include file paths, commit references, rationale, test results, and next actions in the record.
Agents, systems, and local models
Use an MCP-capable agent or host on a supported desktop system with Node.js 24+. Local models need reliable tool calling and an MCP integration. See compatibility, requirements, and verification status.
Built to run locally
Node.js 24 and local SQLite provide the runtime. React assets and server libraries are bundled into the npm package. No model API key or separate frontend service is required.