# What is errata

A local code and knowledge graph for reusing problems, causes, and verified fixes.

Source: https://inerrata.ai/docs/what-is-errata
Updated: 2026-11-05

errata keeps useful debugging knowledge across agent sessions. A daemon maintains a graph for your workspace; supported agent hooks deliver observations and tagged explanations. Future sessions can read relevant context and navigate from a problem to its cause and fix.

## The local loop

1. **Read context.** The daemon maintains `.errata/context.md`. Your agent reads it at task start and queries for more detail.
2. **Investigate.** Code indexing and hook events supply workspace context. Your agent states problems, causes, and fixes using inline capture instructions.
3. **Verify.** Record what failed and what passed after the change. Confirmation and refutation are evidence.
4. **Recall.** Search or walk the graph in a later session instead of repeating the investigation.

The [first-session guide](/docs/your-first-session) checks each part. Capture depends on the integration and transcript format; installing an MCP server alone does not provide hook capture.

## Local graph and shared network

| Surface | What it provides |
| --- | --- |
| Local daemon | Code structure, captured knowledge, context, shell and MCP access |
| Errata Network | Hosted knowledge available to your authenticated identity and scope |
| Console | Account, organization, credentials, installations, and sharing controls |

Your workspace in the Console is where what your agents learn is kept and shared with your team; the daemon is how it gets there and how it comes back. Reads blend your local graph with your workspace and the network. Inspect provenance and scope: another project's lesson is evidence to evaluate, not proof about your code.

## Sharing is a separate choice

Sync is on for a fresh installation: once you sign in, scrubbed lessons reach your workspace. Telemetry starts off. Package contribution starts on and rides sync. A linked repository follows the choices made in its Console link approval.

Contributions pass through scrubbing and generalization controls. Review your identity, target, and consent before sending content; see [Privacy and consent](/docs/privacy-and-consent).

## What a good lesson contains

A useful entry says what failed, why it failed when known, what changed, and how the result was checked. The graph adds connections: a cause behind several symptoms, a fix addressing multiple problems, or a later result contradicting an earlier conclusion.

Start with [Quickstart](/docs/quickstart), then keep the [Agent reference](/docs/agent-reference) handy.