Reli

The learning layer for AI coding agents

Reli learns from developer corrections and adapts AI coding agents to how developers and teams actually build software. Works on top of Cursor, Claude Code, and Codex — not instead of them.

npx @reli1abs/cli

Agents generate code. Reliability still falls on you.

Reli watches file edits and terminal output locally, detects repeated fix patterns, and surfaces workflows you already approved — so corrections compound instead of resetting.

Same mistakes, every session

Agents regenerate the same style, architecture, and debugging mistakes you already fixed last week.

Manual rules drift

Cursor Rules, AGENTS.md, and CLAUDE.md only stay useful if someone keeps rewriting them by hand.

Memory is not a workflow

Storing context is not the same as detecting a correction, approving a reusable fix, and replaying it next time.

How it works

Correction → learned workflow → better future agent behavior. Core runtime stays on your machine.

  1. 01

    Use your agent normally

    Work in Cursor, Claude Code, or Codex inside the editor. Reli does not replace the agent.

  2. 02

    Corrections are observed

    After you opt in, file edits and terminal outcomes are recorded locally — the trail of what actually fixed the failure.

  3. 03

    Repeated patterns surface

    Rule-based detection finds familiar fail→edit→pass loops (tests, types, API/schema). You approve saving the workflow.

  4. 04

    Future sessions improve

    When a similar failure starts again, Reli shows the saved fix summary so the next interaction is informed by what worked.

What runs locally

Local-first means one thing everywhere: on-device storage, local detection, no Reli account, same data format for every capture path.

  • All session data is stored on-device only
  • No code, terminal output, or file contents are sent to a Reli server
  • No user accounts are required for core functionality
  • Pattern detection runs locally in skill-core — no model calls
  • All capture paths write to the same local data format (traces.db + .local-patterns/)
  • What Reli storesSanitized file-edit metadata, terminal commands, exit codes, and error snippets from your session
  • Where data livestraces.db in editor global storage; patterns in .local-patterns/patterns.json in your project
  • What runs locallyCapture, sanitization, loop detection, pattern storage, and replay matching (skill-core)
  • Shared across editorsOne VS Code–compatible extension adapter and one skill-core data format — no per-assistant backends
  • AccountsNot required for core functionality
  • DistributionUnified CLI (npx @reli1abs/cli) downloads the editor extension from static hosting

The learning layer for AI coding agents

Reli is not another coding agent and not a cloud code generator. It captures local events, detects repeated corrections, and stores approved workflows on your machine so every agent you use can become more reliable over time.

  • Local-first runtime

    All session data is stored on-device only Traces and patterns stay on your machine.

  • No account required

    Install the extension, grant consent once, and start coding. Core functionality does not require sign-up or Reli API keys.

  • You control your data

    Secrets are redacted before storage. Sensitive paths like `.env` are skipped. You choose when to save a pattern.

  • Distribution

    The install CLI downloads the extension from static hosting. After install, capture and replay work offline.

Getting started

One command. One click. No accounts, no setup files.

npx @reli1abs/cli

Installs into Cursor and VS Code. Observes Cursor Agent, Claude Code, Codex, Copilot, and other assistants used inside those editors via file + terminal capture. The CLI detects your editor, installs Reli, and can restart it for you.

Use npx @reli1abs/cli — do not install unrelated packages named similarly on npm.

Developing from the repo
npm run reli

The CLI detects Cursor or VS Code, installs Reli as a background learning layer, verifies it, and can restart your editor. Install docs

  1. step 1

    Run one command

    npx @reli1abs/cli installs Reli into Cursor and VS Code and can restart your editor.

  2. step 2

    Click Enable

    When the editor opens, click Enable — or click Reli in the bottom status bar anytime.

  3. step 3

    Keep coding

    That’s it. Reli runs in the background and learns from corrections locally.

FAQ

What is Reli?
The learning layer for AI coding agents. Reli learns from developer corrections and adapts AI coding agents to how developers and teams actually build software. It is not another coding agent, a memory dump, or a rules-file generator.
Why not just use Cursor / Claude / Codex?
Those products build strong agents for generating code. Reli is the reliability layer that learns from how you actually correct them — and can improve behavior across agents, not only inside one vendor’s memory feature.
Where does Reli install?
Into Cursor and VS Code — both are VS Code–compatible hosts. One extension adapter, one skill-core data format.
How do Claude Code, Codex, and Cursor Agent fit in?
Reli does not ship separate adapters per assistant. When you use Cursor Agent, Claude Code, Codex, Copilot, and other assistants used inside those editors, Reli observes the same file edits and terminal commands through the editor extension.
Where is my data stored?
Session traces in SQLite on your machine (traces.db). Saved patterns in .local-patterns/patterns.json in your project. Core runtime does not upload traces or patterns to a Reli server.
What does the MVP detect today?
Repeated debugging loops: test-fix, type-error build cycles, and API/schema failures. Detection runs locally via detectAllLoops() in skill-core — no model calls. Broader habit and team-workflow learning is roadmap.
How do I install?
Node.js 18+ and Cursor or VS Code. Run npx @reli1abs/cli — it detects your editor, installs Reli, verifies the install, and can restart the editor for you. Click Enable on the one-time consent prompt. No Reli account or API key.
Is Reli open source?
MIT licensed. See the GitHub repository for source and issues.