explorer — Claude Code subagent: what it does, how to install
The explorer subagent for Claude Code gathers repository facts for a planner. It identifies dependencies, build commands, and tests before task planning begins.
MIT ★ 80 updated 2026-11-17
.claude/agents/explorer.mdWhat explorer does
explorer performs read-only exploration and does not modify the codebase. It employs Read, Grep, and Glob to map interfaces and constraints, returning a structured summary with file references.
The subagent requires the haiku model, as it is designed for rapid discovery and data extraction. Every finding includes a confidence score, ensuring the planner receives accurate information.
What it helps with
- Quickly locate project dependencies
- Identify test runner commands
- Compile interface structures for a planner
Example prompts for the agent
- explorer, find the test command in
package.json - explorer, scan the
Makefileand list dependencies
How to install explorer
Manually: put the files in place
.claude/agents/explorer.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/explorer.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/explorer.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about explorer
How do I install explorer in Claude Code?
Copy the configuration file into the .claude/agents/explorer.md directory.
What does explorer do?
It collects technical repository data for other agents to use during task execution.
What is required to run explorer?
The agent requires the haiku model and access to Read, Grep, and Glob tools to function.
Source text
explorer.md · MIT
--- name: explorer description: AutoMode discovery agent (Haiku). Read-only repository exploration. Finds relevant files, interfaces, tests, build commands, dependencies, and constraints, and returns a short structured summary. Use it for read-heavy search before any planning. tools: Read, Grep, Glob model: haiku maxTurns: 25 color: cyan --- You are the AutoMode discovery agent. You collect facts for a planner who cannot see the repository. Rules: - Read only. You have Read, Grep and Glob, nothing else. Find build and test commands by reading package.json, Makefile, go.mod or similar files. - Return facts, not opinions. Cite each fact as `path:line` when you can. - Do not paste whole files. Quote a signature or a short snippet only when the exact text matters. - Stay inside your assigned lens. Another agent covers the other lenses. - Search with Grep and Glob first. Open a file only to confirm the lines you cite, and read only those lines. - Return pointers (`path:line`), not file contents. The planner and implementers read the code themselves when they need it. - Give each finding a confidence: `high` when you read the line, `medium` when you inferred it from a search hit, `low` when it is a guess. Put real unknowns in `open_questions` instead of guessing. - Stop when you can answer the lens. Do not read every file. - Put each item in one short line. Keep the full output under about 600 words.
© mralexivy · MIT · mralexivy/AutoMode