Moraine is a local trace stack for agent work. It indexes sessions from agent harnesses such as Codex, Claude Code, Qwen Code, Kiro CLI, Kimi CLI, NAC, OpenCode, Hermes, and Pi Coding Agent into ClickHouse, serves a monitor UI, and exposes MCP retrieval over the indexed history.
Agents get searchable long-term memory through MCP. You get a unified local record of what happened across providers, including tools, tokens, and conversation history.
Moraine is under active development. Config keys, schemas, and MCP tools can change across minor releases.
Moraine ships session trace ingestion adapters for these agent harnesses:
| Harness | Config value | Session traces ingested |
|---|---|---|
| Codex | codex |
JSONL session files under ~/.codex/sessions |
| Claude Code | claude-code |
JSONL project session files under ~/.claude/projects |
| Kiro CLI | kiro-cli |
Paired JSONL transcripts and JSON metadata under $KIRO_HOME/sessions/cli when set, or ~/.kiro/sessions/cli |
| Kimi CLI | kimi-cli |
wire.jsonl session traces under ~/.kimi/sessions |
| Qwen Code | qwen-code |
JSONL chat records under ~/.qwen/projects/*/chats |
| NAC | nac |
Parent sessions and managed-worker episodes from setup-resolved store.db (nac_sqlite format) |
| OpenCode | opencode |
SQLite session history from ~/.local/share/opencode/opencode*.db (default on; opencode_sqlite format) |
| Cursor | cursor |
Agent transcript JSONL under ~/.cursor/projects (default on); Cursor IDE chat history from state.vscdb SQLite databases (default on; cursor_sqlite format) |
| Hermes | hermes |
Live session JSON and trajectory JSONL traces |
| Pi Coding Agent / OMP | pi-coding-agent |
JSONL session trees under ~/.pi/agent/sessions and ~/.omp/agent/sessions |
uv tool install moraine-cli
moraine setup
moraine upmoraine setup creates or repairs ~/.moraine/config.toml and guides plugin or
MCP registration for detected agent harnesses.
For NAC, setup preserves unrelated config.toml settings, registers
[mcp_servers.moraine], and adds the resolved SQLite store only when its path
is stable and absolute. Relative or per-launch --store-path databases require
the manual source snippet printed by setup.
The monitor UI runs at http://127.0.0.1:8080 by default.
For release bundles, upgrades, project-scoped setup, and other harnesses, see the Quickstart and Installation.
Use moraine setup to install or update the Moraine plugins for Claude Code,
Codex, and Hermes; install Kiro CLI's global steering and MCP registration; or
register Moraine MCP for supported harnesses such as Qwen Code, NAC, OpenCode,
Cursor, Kimi CLI, and Pi Coding Agent. The integrations use the moraine CLI on
your PATH and the running local stack. For Kiro CLI, Moraine also resolves the
default kiro ingest source from KIRO_HOME.
Start a new agent session after installing an integration. The Claude Code, Codex, and Hermes plugins provide named Moraine skills. Kiro CLI receives equivalent search and realtime guidance from its managed global steering file. Moraine MCP tools are exposed with each harness's MCP naming scheme. Then ask:
What are my agents doing right now?
The user-scoped plugins can search the host-wide Moraine history visible to your user. For project-scoped setup, duplicate MCP cleanup, and other clients, see Agent MCP Search.
The Claude Code, Codex, and Hermes plugins already bundle Moraine search
guidance, and moraine setup --mcp-target kiro-cli installs it under
$KIRO_HOME/steering when set, or ~/.kiro/steering otherwise. If you use
manual MCP registration or another harness, add the following guidance to its
global instructions, such
as that Kiro steering path, ~/.codex/AGENTS.md for Codex, or
~/.claude/CLAUDE.md for Claude Code:
- You have access to all past agent sessions (whether codex, claude, hermes, etc., anything) via moraine search tools.
- Any time the user asks about information not located within your context, that you can't see or don't know, but implies that you *should* know, it is because it was a past conversation. You can reference and search for this conversation with moraine search tools or session listing.
- Moraine search tooling is built around BM25 keyword search, so target your queries to keywords rather than questions. There is no semantic search.
- Successful keyword searches often go from broad to narrow. Sometimes this narrowing isn't successful, in which case, you can always back up and try a different path.
- Moraine has a *real-time* view of agent sessions. You can use it to peek on active AI agent sessions, including your own, sessions running in different harnesses, sessions that are sub-agents of your current conversation, or even their subagents. All agent work, in realtime, is visible to you.With this you can do operations like the following:
claude -p "What are my agents doing right now?"
codex exec "What are my agents doing right now?"
hermes -z "What are my agents doing right now?"
kiro-cli chat --no-interactive "What are my agents doing right now?"
cargo build --workspace --locked
cargo test --workspace --locked
cargo fmt --all -- --checkThe repository-managed pre-commit hook can be installed with:
make hooks-installMoraine contributor workflows are available through the repository's Codex plugin and Kiro workspace agent with native Agent Skills. See Agent Contributor Workflows for installation and usage.
To put the current checkout (tip-of-branch, no tagged release needed) onto your
host for testing, build and install it over the active moraine on your PATH:
make installThis release-builds the host target and installs through the same
scripts/install.sh path end users get. ClickHouse is skipped by default
(make install INSTALL_ARGS="--with-clickhouse" to include it). See
scripts/dev/install-host.sh --help for the full set of options.