Ai Hist

Sync and search your Claude Code, Codex CLI, Cursor, Grok, Agent Relay, and compacted persona trajectory history into a local SQLite database with full-text search.

ai-hist is a Rust CLI. New commands and integrations should land in the Rust SDK/CLI surfaces.

Why ai-hist

Coding agents start every session from zero — they can't see the decisions you made yesterday, the approach that already failed, or the reasoning behind the architecture they're editing. Local transcript search recovers what you typed. ai-hist also captures why.

• HOW + WHY, not just HOW. Most history tools index raw prompts and transcripts (the how). ai-hist indexes those and distilled trajectories — the decisions (question → chosen → reasoning → alternatives) and retrospectives (learnings, confidence) behind each run. Ask why_for_task and get the reasoning, not just the keystrokes.
• Local-first, team-optional. Everything lands in local SQLite with FTS5 — no keys, no network required. When you want it, opt into cloud sync to feed a shared team memory with server-side secret/PII scrubbing and a self-host Enterprise tier.
• It talks back. Pushed history powers Pair: before a risky action, your agent queries the store and gets cited warnings drawn from your team's own prior work — so nobody repeats a mistake that's already in the record.
• Built for agents. A stdio MCP server (npx -y ai-hist-mcp) exposes search_history, get_context, search_trajectories, and why_for_task so the agent can pull its own context mid-session, scoped to one project.

If you only want fast local grep over your own agent history, ai-hist does that in one command. The trajectory + Pair loop is there when you're ready for team memory that prevents repeat mistakes.

Install

curl -fsSL https://raw.githubusercontent.com/AgentWorkforce/relayhistory/main/install.sh | sh

Make sure ~/.local/bin is in your PATH:

export PATH="$HOME/.local/bin:$PATH"  # add to .zshrc / .bashrc

The installer installs deterministic launchers for ai-hist and ai-hist-rust. For normal installs it downloads a prebuilt Rust binary from GitHub Releases, so users do not need a local Rust toolchain.

If no prebuilt binary is available for your platform, the installer falls back to building from source. That fallback requires cargo; install Rust from https://rustup.rs/ if you intentionally use the source path.

Installer controls:

curl -fsSL https://raw.githubusercontent.com/AgentWorkforce/relayhistory/main/install.sh | AI_HIST_INSTALL_METHOD=binary sh
curl -fsSL https://raw.githubusercontent.com/AgentWorkforce/relayhistory/main/install.sh | AI_HIST_VERSION=0.3.5 sh
AI_HIST_INSTALL_METHOD=source sh install.sh   # from a local checkout
AI_HIST_SOURCE_REF=my-branch sh install.sh    # override source fallback ref

The publish workflow creates the npm packages, the sdk-ts-v<version> GitHub Release, and the prebuilt Rust assets consumed by the installer.

Usage

# Import all history (incremental — only reads new bytes on re-run)
ai-hist sync

# Full-text search
ai-hist search "authentication bug"
ai-hist search "refactor" --source claude --limit 10
ai-hist search "deploy" --source relay
ai-hist search "retry policy" --source trajectory
ai-hist search "deploy" --project relay
ai-hist search --tag relayfile-migration

# Recent prompts
ai-hist recent                             # last 20
ai-hist recent 50                          # last 50
ai-hist recent --source claude --project my-app

# Drill into a specific entry (shows full prompt + metadata + resume command)
ai-hist show 4521

# See surrounding context (same session + nearby entries)
ai-hist context 4521
ai-hist context 4521 --window 15   # ±15 min window (default: 5)

# View all prompts in a session
ai-hist session abc-1234-def
ai-hist session abc-1234-def --full   # no truncation

# Resume a conversation directly (the exact command is shown by `ai-hist show <id>`)
cd /path/to/project && claude --resume <session_id>          # claude
codex resume <session_id>                                     # codex
cd /path/to/project && cursor-agent --resume=<session_id>    # cursor

# Stats overview
ai-hist stats

Search results include entry IDs (#NNN) — use them to drill deeper:

ai-hist search "deploy" → find #4521
ai-hist show 4521       → see full prompt, session info, resume command
ai-hist context 4521    → see what else was happening in that session + nearby
ai-hist session <id>    → browse the full conversation

Example output from ai-hist stats:

Total entries: 47,665

By source:
  claude: 37,406
  codex: 10,259

Date range:
  2025-10-05 to 2026-03-08

Top 10 projects:
   8,701  /Users/you/Projects/my-app
   4,586  /Users/you/Projects/api-server
   ...

How it works

ai-hist supports these sources:

Source	How	Key fields
Claude Code	Local JSONL (~/.claude/history.jsonl)	display, timestamp, project, sessionId
Codex CLI	Local JSONL (~/.codex/history.jsonl)	text, ts, session_id
Cursor	Per-session JSONL (~/.cursor/projects/<encoded-path>/agent-transcripts/<uuid>/<uuid>.jsonl)	role, message.content[].text (user prompts wrapped in <user_query>...)
Grok	Per-session JSONL (~/.grok/sessions/<encoded-path>/<session-id>/chat_history.jsonl) plus summary.json	type, content[].text, info.cwd, head_branch
Agent Relay	API (https://api.relaycast.dev/v1)	sender, content, channel, timestamp
Trajectories	Compacted per-run JSON ($TRAJECTORY_ROOT/**/compacted/*.json)	personaId, projectId, task, decisions, retrospective
OpenCode	Local SQLite ($OPENCODE_DB or ~/.local/share/opencode/opencode.db)	user text parts joined to sessions

Claude Code, Codex, Cursor & Grok are synced from local JSONL files incrementally. Grok user prompts are read from chat_history.jsonl; synthetic reminders are skipped and session metadata comes from summary.json.

Agent Relay is synced via the Relaycast API, pulling workspace messages with cursor-based pagination. Configure with:

export RELAYCAST_API_KEY="rk_live_..."
export RELAYCAST_WORKSPACE_ID="ws_abc123"

Trajectories are synced from compacted per-run JSON files. Configure an explicit root with:

export TRAJECTORY_ROOT="/path/to/repo/.trajectories"

ai-hist scans $TRAJECTORY_ROOT/**/compacted/*.json. Without TRAJECTORY_ROOT, it discovers ~/Projects/**/.trajectories/**/compacted/*.json.

The runtime contract is one JSON file per completed run:

{
  "id": "run-id",
  "version": 1,
  "personaId": "planner",
  "projectId": "agent-workforce",
  "task": { "title": "Task title", "description": "Task description" },
  "status": "completed",
  "startedAt": "2026-06-06T10:00:00.000Z",
  "completedAt": "2026-06-06T10:05:00.000Z",
  "decisions": [
    {
      "question": "What should we do?",
      "chosen": "Chosen option",
      "reasoning": "Why this option won",
      "alternatives": ["Other option"]
    }
  ],
  "retrospective": {
    "summary": "What happened",
    "approach": "How the work was done",
    "learnings": ["What to carry forward"],
    "confidence": 0.8
  }
}

Aggregate trail compact artifacts are intentionally not the ai-hist interface; ai-hist indexes the runtime-emitted per-run contract files.

All sources are indexed with FTS5 full-text search. Deduplication uses INSERT OR IGNORE on a UNIQUE(source, timestamp_ms, prompt) constraint.

Database location

Default: ~/.local/share/ai-hist/ai-history.db

Override with the AI_HIST_DB environment variable:

export AI_HIST_DB="$HOME/Dropbox/ai-history/ai-history.db"

MCP server

The TypeScript package exposes a stdio MCP server that wraps the SDK and serves both HOW history and WHY trajectories:

npx -y ai-hist-mcp

Tools include search_history, recent_entries, get_session, get_context, stats, search_trajectories, and why_for_task.

To scope the MCP server to one project, pass a project scope when launching it. The scope includes exact matches and child paths, so /path/to/project also includes sessions recorded under /path/to/project/packages/api.

npx -y ai-hist-mcp --project .
npx -y ai-hist-mcp --project /path/to/project

Continuous sync

The installer sets up a background sync service automatically, so history stays fresh without any manual step. To opt out at install time, set AI_HIST_NO_AUTOSYNC=1.

To manage it yourself at any time:

ai-hist sync --install-service    # launchd on macOS, cron on Linux
ai-hist sync --uninstall-service  # remove it
ai-hist sync                      # run a one-off sync now
ai-hist import --watch            # foreground alias for continuous live capture

--install-service points the scheduler directly at the resolved ai-hist binary (no shell wrapper, no python3) and reloads idempotently, so it can't fall into the stale-interpreter trap the hand-written plist below historically hit. On macOS, pass --interval <seconds> to change the cadence (default 60; cron runs at 1-minute granularity). Verify health with:

launchctl list | grep ai-hist   # middle "last exit status" column should be 0

Continuous cloud push

sync keeps the local database fresh. Uploading it to relayhistory-cloud is a separate step (push), which has its own background service using the same launchd/cron plumbing:

ai-hist push --install-service      # schedule automatic cloud push (macOS: every 300s)
ai-hist push --uninstall-service    # remove it
ai-hist push                        # push new history now

On macOS the launchd job honors --interval (default 300s). On Linux the job is a cron entry: whole-minute intervals become a step schedule (300s → */5), and sub-minute intervals run every minute (cron's finest granularity).

Running both services keeps local capture and cloud upload going end-to-end. The push job authenticates with the rth_at_ token written by ai-hist login.

Manual setup (macOS)

If you prefer to write the launchd plist by hand, sync every 60 seconds with:

The unquoted heredoc (<< EOF) expands $HOME to an absolute path as the file is written — launchd does not expand ${HOME} in ProgramArguments, so the path must be literal. Point it directly at the ai-hist wrapper; do not prefix it with python3 (the wrapper dispatches to the Rust binary itself).

cat > ~/Library/LaunchAgents/com.ai-hist.sync.plist << EOF
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>Label</key>
    <string>com.ai-hist.sync</string>
    <key>ProgramArguments</key>
    <array>
        <string>$HOME/.local/bin/ai-hist</string>
        <string>sync</string>
    </array>
    <key>StartInterval</key>
    <integer>60</integer>
    <key>RunAtLoad</key>
    <true/>
    <key>StandardOutPath</key>
    <string>/tmp/ai-hist-sync.log</string>
    <key>StandardErrorPath</key>
    <string>/tmp/ai-hist-sync.err</string>
</dict>
</plist>
EOF

# Reload (idempotent — unload any previous version first)
launchctl unload ~/Library/LaunchAgents/com.ai-hist.sync.plist 2>/dev/null
launchctl load ~/Library/LaunchAgents/com.ai-hist.sync.plist

Replace $HOME/.local/bin/ai-hist with the wrapper path you installed if needed, then confirm the job is healthy with launchctl list | grep ai-hist (the middle "last exit status" column should be 0, not 1).

Manual setup (Linux, cron)

# Sync every minute
echo "* * * * * ~/.local/bin/ai-hist sync >> /tmp/ai-hist-sync.log 2>&1" | crontab -

Alternative: watch mode

ai-hist watch              # syncs every 60s
ai-hist watch --interval 30  # syncs every 30s
ai-hist import --watch --interval 30

Session → commit links

ai-hist can record local, no-network links between captured agent sessions and git commits. The rows are raw evidence for downstream outcome attribution: they contain match method, confidence, changed files, numstat, and evidence JSON. They do not score work quality.

Install the hook in a repo:

ai-hist setup git --repo /path/to/repo

After each commit, the managed post-commit hook runs ai-hist link commit, stores a row in session_commit_links, and may write a local refs/notes/ai-hist note when Git accepts the note write. note_ref is nullable so link rows remain valid when notes are disabled or cannot be written. To link manually:

ai-hist link commit --repo /path/to/repo --commit HEAD --json

Export links for Reflex or another consumer:

ai-hist export commit-links --jsonl --since 2026-06-01

Each JSONL row includes:

{
  "source": "claude",
  "session_id": "session-id",
  "repo": "/path/to/repo",
  "branch": "feature-branch",
  "commit_sha": "abc123...",
  "note_ref": "refs/notes/ai-hist",
  "match_method": "git_note",
  "confidence": 0.95,
  "files_json": ["src/file.rs"],
  "numstat_json": [{"path": "src/file.rs", "additions": 10, "deletions": 2}],
  "evidence_json": {"candidate": {"branch_match": true}},
  "created_at_ms": 1780000000000
}

Schema

CREATE TABLE history (
    id INTEGER PRIMARY KEY AUTOINCREMENT,
    source TEXT NOT NULL,          -- 'claude', 'codex', 'cursor', 'grok', 'relay', 'trajectory', or 'opencode'
    session_id TEXT,
    project TEXT,
    prompt TEXT NOT NULL,
    timestamp_ms INTEGER NOT NULL,
    UNIQUE(source, timestamp_ms, prompt)
);

-- FTS5 full-text search index
CREATE VIRTUAL TABLE history_fts USING fts5(prompt, project, content='history', content_rowid='id');

Trajectory sync also maintains a structured trajectories table for decisions and retrospectives, while inserting a searchable source='trajectory' row into history.

You can query the database directly with any SQLite client:

sqlite3 ~/.local/share/ai-hist/ai-history.db "SELECT COUNT(*) FROM history"

License

MIT