Configuration

agentgrep is intentionally low-configuration. It reads known local agent stores under the current user’s home directory and never mutates them.

Agent selection

Use --agent one or more times to limit search or discovery:

$ uv run agentgrep grep "cache" --agent codex

Supported agents are codex, claude, cursor-cli, cursor-ide, gemini, antigravity-cli, antigravity-ide, grok, pi, opencode, and vscode. Omitting --agent searches all supported agents. Windsurf storage is documented but unsupported (its conversations are encrypted); see Unsupported backends.

Search scope

Search and grep default to prompt scope: user-authored prompts, including dedicated prompt-history logs and user turns projected from transcript-only stores. Use --scope to opt into broader records:

$ uv run agentgrep grep "docs deploy" --scope conversations

Or search both surfaces at once:

$ uv run agentgrep grep "docs deploy" --scope all

Allowed values are prompts, conversations, and all.

Output

Text output is optimized for terminal reading:

$ uv run agentgrep grep "release"

Use JSON or NDJSON for scripts:

$ uv run agentgrep grep "release" --json
$ uv run agentgrep grep "release" --ndjson

Progress and early answers

Human text searches show progress by default. Press Enter on a blank line to return the matches collected so far.

$ uv run agentgrep grep "bliss" --progress always

Disable progress when scripting:

$ uv run agentgrep grep "bliss" --progress never

Privacy

Serialized paths are protected before leaving the process. Home-relative paths are displayed as ~/..., and directory paths keep a trailing /, for example ~/.codex/sessions/.

MCP capabilities

MCP clients can read agentgrep://capabilities to inspect supported agents, adapters, tools, resources, prompts, and selected optional backends.