Start

Ludion tells your coding assistant what changed in the versions your project installed. Each change is checked by a machine and signed by the person who taught it.

In Claude Code

/plugin marketplace add Ludion-ai/ludion
/plugin install ludion@ludion

The plugin runs ludion sync at the start of every session and adds the Ludion MCP server (ludion_ask, ludion_teach).

With any assistant

npx ludion-ai sync

Run it in your project, and again after you upgrade. It reads your lockfile and writes .ludion/lessons.md, imports it from CLAUDE.md, names it in AGENTS.md if you have one, and adds a Cursor rule if you use Cursor.

Just the MCP server

claude mcp add --transport http ludion https://ludion.ai/mcp

Teach a lesson

npx ludion-ai teach draft.json
npx ludion-ai teach draft.json --public

When your assistant gets a change wrong, ask it to draft a lesson with ludion_teach, then run the command it gives you. ludion teach shows you the whole lesson, checks its sources, runs its tests only in Docker, and saves it to your ledger, so sync writes it in every project on your machine that installs a matching version. Add --public to open a pull request in your own name; CI checks it again, and a maintainer merges it.

What leaves your machine

sync downloads the lesson lists for the packages in your lockfile, and nothing else. No telemetry. teach fetches the source pages it cites, and --public uses your own gh. Through the MCP server, ludion_ask sends your question to ludion.ai, and ludion_teach sends the draft.