Skip to content

getting-started.md

Latest commit

 

History

History
66 lines (43 loc) · 3.17 KB

getting-started.md

File metadata and controls

66 lines (43 loc) · 3.17 KB
Raw

Getting started

Origin runs on your machine. It reads the session logs your AI agents already write to disk, archives them in ~/.origin, and serves them to every agent through one MCP server. If you use agents on several machines, a self-hosted personal hub can bring them together later.

::: warning Early version Origin is not at 1.0 yet. Until then, a new minor version may change the store format: stores are upgraded in place, and Upgrading and the changelog say what to do. :::

Requirements

  • Node.js 22.16 or later (24 LTS recommended)
  • At least one supported agent: Claude Code, Codex CLI, Cursor, Grok Build, or ZCode.

Install

npm install -g @openlinkos/origin
origin --version

This puts the origin command on your PATH. To work on Origin itself, build it from source as described in CONTRIBUTING.md.

Archive your sessions

origin sync      # ingest local agent sessions into ~/.origin
origin status    # sessions, events, and entries per source
origin timeline  # sessions from the last 7 days

sync is incremental and safe to re-run. When agents use Origin over MCP, the server syncs on its own, so you rarely need to run sync by hand. It also imports the memories that Claude Code, ZCode, and Grok Build keep for themselves, as entries that follow their files (see Native memories).

Connect an agent

Register Origin once, at user scope, so that every project shares the same memory. For Claude Code:

claude mcp add --scope user origin -- origin mcp
claude mcp list   # origin: … ✔ Connected

On Windows, npm installs origin as a .cmd script that agents cannot start directly; register cmd /c origin mcp instead, for example claude mcp add --scope user origin -- cmd /c origin mcp.

Other agents are covered in Connect your agents.

Ask

Start a new session and ask about your past work, for example:

What did I decide about schema migrations in the origin project last week, and why? Cite your sources.

The agent searches Origin and answers with entry and event ids. To read the original, run origin show <id>. When the agent learns something worth keeping (a decision and its reason, a stable fact, or one of your preferences), it saves an entry with remember.

Curate your memory

origin entries                           # what agents have remembered
origin show ent_5f0c2a9e41b7             # an entry with its sources and history
origin correct ent_5f0c2a9e41b7 "…"      # replace it with a corrected version
origin forget ent_5f0c2a9e41b7 --reason "wrong" --yes   # hide it everywhere, as a record
origin restore tmb_3a9d70c1e2f4 --reason "needed" --yes  # bring it back

To do the same in your browser, run origin ui: it opens the admin UI for the store on this machine, on 127.0.0.1, with a one-time sign-in link.

See the CLI reference for every command, and Privacy and your data for what Origin stores and how forgetting works.