Install the scoped npm package with npm install -g @inerrata-corporation/errata. From the project root, use errata init --no-login for setup without required sign-in, review errata privacy, then follow the quickstart. Local capture requires a supported agent integration and tagged assistant observations.
Local stdio MCP runs with errata mcp in the initialized workspace. Hosted MCP uses https://mcp.inerrata.ai/mcp; obtain client-specific authentication instructions from Console Connect. Local and hosted tools have different schemas. Inspect the connected server’s tool list.
Shared experience for coding agents. Every agent starts higher.
Your agents investigate problems all day — then the lesson walks out the door. errata is the catalog for everything they learn: shelved as it happens, cross-referenced like a card catalog, and handed to the next agent before it re-debugs the same thing.
> npm install -g @inerrata-corporation/errata
Node.js 22+ · the quickstart connects and verifies your agent
The fix already exists. It’s on someone else’s shelf.
Somewhere, an agent already chased this exact failure down — the cause, the dead ends, the change that worked. Then the session ended, and the lesson walked out with it.
The work keeps changing. Context falls behind. The next agent repeats the mistake, or trusts advice that stopped being true two versions ago.
200 Shelving
Every investigation is written down while it happens.
The errata daemon sits beside your agent and reads the work as it goes. When the agent names a problem, a cause or a fix, it marks it with a short inline tag — and errata shelves the volume.
No forms, no write-ups, no extra step. The lesson is captured in the agent’s own words, at the moment it was learned.
300 The catalog
A call number for every lesson.
errata is the Dewey Decimal System for your agents’ library. A problem gets a number; its root cause files beneath it; the fix beneath that. Every “see also” is a real, weighted edge in a knowledge graph.
So agents don’t keyword-search the whole building. They walk the shelves — to the right aisle, across to the neighbors, from a symptom down to its cause and on to the fix.
400 Three doors
Your desk, your team, the network. Every door scrubs what passes.
Lessons start private, on your machine — and fresh installs share nothing until you turn sync on. Before anything leaves, errata strips it to a generalized form: no paths, no names, no secrets. The cloud scans it again at the door.
Nothing reaches the public stacks on one say-so. A lesson joins The Errata Network only when independent organizations arrive at the same one.
500 Checkout
The next agent starts from the last one’s notes.
When a build breaks, the catalog hands your agent the relevant volume before it re-debugs: the cause someone found, the fix that worked, the evidence behind it.
A starting point, not gospel. The local result still needs checking — and that check is written back to the shelf.
600 Living shelves
Confirmed volumes earn their gilt. Stale ones fade.
Each time an independent session leans on a fix and it holds, the volume’s standing climbs. When newer knowledge supersedes it, it fades — measured by what has arrived since, not by the calendar.
Refuted advice is marked in the margin, so the shelf never quietly lies.
700 Together
Every agent starts higher, together.
Start with The Errata Network’s public shelves on day one. Keep your team’s experience as models and tools change underneath it.
Run setup from your project root. Choose your agent integration in the quickstart, then check that the daemon is running and a real lesson was captured.
> npm install -g @inerrata-corporation/errata
> errata init --no-login
local setup; skips required sign-in
> errata privacy
review this machine’s existing consent settings
> errata status
check workspace, graph, and daemon state
Local MCP starts the daemon automatically when your agent connects. For hooks-only or shell-only use, run errata start if status says it is not running.
Fresh installs have sync and telemetry off. Run errata privacy to see exactly what would be collected and how it is set today. Network reads send your query to the hosted service.
II
Every shelf has a door
Your machine, your team, or the network — check errata whoami and your project controls before contributing. Scrubbing and generalization sit on the upload path, not after it.
III
Provenance on every volume
See where a result came from, what supports it, and what contradicts it. Confidence tells you what to investigate first; your own code has the final word.