AI Session Search CLI
The aise utility searches local session history of Claude Code, Codex, Cursor and six more agents and serves it over MCP.
- 52 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- The index reads whole local sessions, which often contain passwords and keys.
- The integrations command edits MCP configuration and the `CLAUDE.md` and `AGENTS.md` files.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/ai-session-searchDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The index reads whole local sessions, which often contain passwords and keys.
- The integrations command edits MCP configuration and the `CLAUDE.md` and `AGENTS.md` files.
This is third-party code. Review the repository files before installing.
What it does
The Rust utility `aise` parses sessions from nine agents into a single index and refreshes it on the fly. From that index you can find a conversation or a single message, recover a file an agent once wrote, or see why a run stopped. The index is reachable four ways: the command line, the `aise tui` text interface, a Python package and a Rust crate. The built-in MCP server gives an agent `search_sessions`, `search_messages`, `get_session` and a read-only SQL tool `query_session_index`, so the agent can answer questions about past sessions itself.
Who it is for. People who run many AI-agent sessions and lose decisions, commands and file versions inside them.
Good fit when
- You recall a session a month ago about an auth refactor and search it with `aise search "auth refactor"`.
- An agent overwrote a file and the old version survives only in a log; `aise files extract src/app.py --restore` pulls it out.
- A run stopped on a hook or a block, and `aise messages search "" --kinds harness-notice` shows why.
- You want to know what a subagent was asked and what it found: `aise list --session-kinds subagent` helps.
- Details vanished after context compaction, and `aise messages evidence SESSION_ID` brings them back.
Not a fit when
- The history lives in the agent cloud, not on disk: `aise` reads only local files.
- Sessions contain secrets that must not be shown to an agent even locally.
- You need search in one agent where the built-in `/resume` is enough.
Example request
Find the session where we fixed the database migration, show its last messages and give me the command to resume it.Limitations
The index is built from local session files of supported agents and reads everything stored there, including pasted keys and passwords. `aise integrations install` edits MCP configuration and adds blocks to `CLAUDE.md`, `AGENTS.md` and `GEMINI.md`, so run it with `--dry-run` first. No hooks are installed. MCP tools change nothing in sessions or settings, and a recovered file lands beside the original with a `.recovered` suffix.
How to disable. Check connections with `aise integrations status`, delete the blocks from `CLAUDE.md`, `AGENTS.md` and the MCP entries, then run `uv tool uninstall ai-session-search`. Delete the index separately; `aise config paths` shows where it is.
FAQ
Which agents does `aise` read?
Claude Code, Claude Desktop, ChatGPT Codex, Cursor, Antigravity, Pi, Prime Agent, Google AI Studio and Gemini CLI on macOS, Linux and Windows.
How do I connect the MCP server?
Run `aise integrations install`: it registers the server with each detected agent. To start it by hand, use `aise mcp serve` over stdio.
How do I recover a lost file?
`aise files history src/app.py` lists versions and `aise files extract src/app.py --restore` writes the result to a sibling `.recovered` file without overwriting anything.
Can I install it with Cargo?
Yes: `cargo install ai-session-search --locked && aise integrations install`.
How do I check that the index is healthy?
Run `aise doctor` for index state and `aise config paths` for paths. You can build the first index ahead of time with `aise reindex`.
Discussion
No questions or reviews yet.
Related
CLI toolsA CLI that gathers Claude Code and Codex session history into a local graph, searches it and turns repeated mistakes into fixes
Every Claude Code, Codex and other agent session in one search: lossless storage you own, with MCP, CLI, HTTP and SQL access
A skill for searching past sessions: a full-text index of Claude Code, Codex, pi and Grok chats in one SQLite database
An fzf-based CLI that lists sessions of Claude Code, Codex and six more agents across projects and resumes the chosen one.
Terminal search across Claude Code, Codex, OpenCode and other agent sessions, with a jump back into the right chat
claude-history searches and opens past Claude Code, Codex and Pi conversations in the terminal and gives Claude a history skill
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| AI Session Search (this card) | no | not required | 52 | |
| Coding Agent Session Search (cass) | no | 1,205 | a similar agent session search; aise adds file version recovery and harness notices | |
| claude-history | no | 542 | searches one Claude Code history; aise puts nine agents in one index |
README in short
The project searches sessions from the command line, a terminal UI, Python, Rust and MCP. The integrations step prepares configuration and guidance for each agent.