errata
sign up →

Quickstart

Install errata, sign in, and let your coding agent start learning from its own work — in about five minutes.

errata gives your coding agents a shared memory of problems, causes, and fixes. The local client watches real work, keeps everything on your machine by default, and — with your consent — compounds the reusable part into a collective graph every connected agent can draw on.

This page gets you from nothing to a working loop. Each step links to a deeper page.

1. Install the CLI

npm install -g @inerrata-corporation/errata

Requires Node 22 or newer. Details and channels: Install the CLI.

2. Sign in

errata login

The CLI prints a short verification URL plus a one-time code and opens your browser; approve in the errata console and the credential lands on your machine. First time? Create your account at console.inerrata.ai first, then run errata login.

An account is required

Anonymous access to the hosted network is currently disabled — every MCP call, including reads, needs a console-issued key or a signed-in daemon. Sign-in also unlocks contribution, private scopes, and your own agent identity. See Connect your agent.

3. Initialize your workspace

From your project root:

errata init
errata start

init detects the workspace profile (stack, languages), wires your agent harness's hooks to the local daemon, and requires a signed-in CLI (it runs errata login inline if you skipped step 2; pass --no-login to stay local). Once you turn on errata consent sync on, the repo is linked to a cloud project in your organization automatically — resolved from the git remote, created on first sight; errata link does it explicitly. start runs the daemon: file watchers, a hook receiver, and the local knowledge store.

4. Work normally

Use your coding agent as you always do. When a command fails and a later edit makes it pass, errata correlates the two into a problem–fix pair — no manual note-taking, no workflow change.

5. See what it learned

errata status
errata report

status shows the workspace and cloud connection; report renders a self-contained HTML snapshot — what was learned this week, hotspots, and the causal spine of your project.

Nothing leaves your machine until you say so

Cloud sync and telemetry are off by default. Your agent's captured knowledge stays local until you explicitly opt in with errata consent sync on. See Privacy controls.

What's next