Ori-Mnemos

Quick Start

npm install -g ori-memory
ori init my-agent
cd my-agent

Connect to your agent:

---

# Infrastructure
ori index build [--force]         # Build embedding index
ori index status                  # Index statistics
ori graph metrics                 # PageRank, centrality
ori graph communities             # Louvain clustering
ori serve --mcp [--vault <path>]                                # Run MCP server
ori bridge claude-code [--scope <s>] [--activation <a>] [--vault <p>]  # Claude Code (hooks + MCP + instructions)
ori bridge hermes [--scope <s>] [--activation <a>] [--vault <p>]       # Hermes Agent (plugin + MCP + instructions)
ori bridge opencode [--scope <s>] [--activation <a>] [--vault <p>]     # OpenCode (plugin + MCP + AGENTS.md)
ori bridge cursor [--scope <s>] [--vault <p>]                          # Cursor (MCP config)
ori bridge codex [--scope <s>] [--vault <p>]                           # Codex (TOML config)
ori bridge generic [--scope <s>] [--vault <p>] [--json]                # Any MCP client (prints config)
ori bridge status [--json]                                             # Inspect all bridge installs
ori bridge <target> --uninstall                                        # Remove Ori config for a target

Path-taking commands treat relative file paths as vault-relative. Absolute paths continue to work unchanged.

Deployment

Local. Install globally, ori init, connect your MCP client. Done.

VPS / headless. Install on the server. ori serve --mcp --vault /path/to/vault. Memory persists on the filesystem. Back up with git push.

Remote terminals. Hermes Agent supports Docker, SSH, Modal, and Daytona backends. If your agent runs in a remote terminal, ori must be installed and on PATH inside that environment, and the vault must be on persistent storage (not ephemeral). For serverless backends like Modal where environments hibernate, mount the vault on a persistent volume.

Multi-vault. Separate Ori instances for separate agents. Each vault is self-contained: its own identity, knowledge graph, and operational state.

Scriptable. CLI returns structured JSON. Use in cron jobs, webhook handlers, or orchestration loops.

Install Model

Ori separates three install concepts:

• scope: global follows one vault across the machine, project stays inside one repo/workspace
• activation: auto runs ori_orient at session start where the adapter supports it, manual leaves tools available but does not auto-orient
• vault: explicit --vault wins; otherwise Ori resolves by install scope

Precedence rules:

• project install overrides global install
• explicit --vault overrides inferred vault
• project activation overrides global activation

Bridge lifecycle:

• rerun the same ori bridge ... command to update vault path or activation in place
• use --uninstall to remove Ori-owned config from supported adapters
• generic installs emit manual uninstall instructions because Ori does not own that client config surface

Claude Code, Hermes Agent, and OpenCode are fully automated adapters with lifecycle hooks. Claude Code uses hook scripts; Hermes uses a native Python plugin installed at ~/.hermes/plugins/ori/; OpenCode uses a JavaScript plugin at .opencode/plugins/lifecycle.js. All three auto-orient at session start (via first-run detection) and capture insights at session idle. Cursor and Codex have native MCP config install support. Codex writes to ~/.codex/config.toml and uses a single global config surface; "project" scope there means project-like runtime vault discovery, not a separate project config file. Other MCP-capable clients can use ori bridge generic now and wire the emitted config into their own client surface.

License

Apache-2.0

Memory is sovereignty. Ori gives your agent a mind.