About
We're building the local workbench for agentic software work.
eri started as a side project: one engineer, a repo, and the hunch that serious agent work needed to live closer to the files, commands, and review habits developers already trust.
Why eri exists
The first wave of coding assistants made autocomplete dramatically better. The second wave gave us chat sidebars. Both still treated the terminal, editor, issue context, and deployment path as separate places. We think the useful frame is a workbench: one local loop where an agent can inspect, edit, run, explain, and ask before handing work to the cloud.
eri is not a generic editor skin or a wrapper around a remote API. It is a local product surface for agentic work: files, diffs, terminal output, task history, voice input, and cloud handoff arranged around the developer's review loop.
Manifesto
Four things we won't do.
We started eri because the tools we used every day kept making choices we wouldn't have made for ourselves. So we wrote them down. These are the four lines we don't blur.
We don't want your repo on our servers. Your project lives on your laptop unless you deliberately hand off a task to cloud runtime.
We don't want to sell your usage data. We don't have an ad model. We don't sell prompts, outputs, command logs, or telemetry. If we ever change this, we'll tell you in plain English first, not in a Terms update.
We don't want invisible automation. Agent turns should show what changed, what ran, what failed, and what gets sent outside the machine before it leaves.
We don't want surprise bills. Paid tiers are hard-capped at their monthly headline price. When you hit the cap, eri stops metered cloud turns instead of inventing an overage line item.
What we believe
Intent is the input layer
Some work starts as a sentence, some as a selected file, some as a terminal failure. eri turns that intent into a reviewed plan, a working diff, or the next command without making you leave the workspace.
The loop is local
Project files, edit history, voice transcription, command output, and review state live on your machine. Cloud services are an explicit handoff for work that needs remote compute, longer runs, or a hosted environment.
The CLI is part of the product
Agents should be able to inspect files, run commands, read failures, and propose the next step. eri treats the terminal as first-class context instead of a window you copy errors out of.
Who we are
One person building in public. The weeks that went well and the weeks that didn't both get posted. Email gets answered. Fridays ship anyway.
Based in Ontario, Canada. Independent. Self-funded. Provided as-is.