Skip to main content
subagent CX Codex

docs-researcher — Codex subagent: what it does, how to install

docs-researcher — a subagent that verifies APIs, version-specific behavior and framework options against official documentation.

MIT ★ 6,505 updated 2026-10-05

Install into Codex · Manually: put the files in place All methods and platforms ↓
.codex/agents/docs-researcher.toml
Open on GitHub

What docs-researcher does

Activates when a task needs a precise answer from documentation: method semantics, default values, version-dependent behavior, or configuration options. Locates the relevant section in primary sources, extracts facts with exact references and returns a verified answer. Distinguishes documented behavior from inference.

Works in four steps: identifies the question and versions in scope, finds relevant documentation sections, extracts defaults and caveats, returns verified answer with ambiguity flags and follow-up validation steps. Does not change code or speculate beyond documentation text unless the parent agent explicitly requests it.

Returns an answer with precise references for each key point, version context, unresolved ambiguity and confidence level. When documentation is inconclusive, recommends what to validate at runtime.

What it helps with

  • verify API semantics and parameter behavior from documentation
  • find default values and implicit behavior that surprises implementers
  • identify version-specific differences and migration requirements
  • extract error modes and operational caveats from official sources
  • separate documented facts from assumptions

Example prompts for the agent

  • What are the default parameters for the fetchUser method in libxyz version 2.4?
  • Check the docs for changes in OPTIONS behavior between Django 4.2 and 5.0.
  • Look up when useEffect fires twice in StrictMode in React 18 documentation.

How to install docs-researcher

Manually: put the files in place

.codex/agents/docs-researcher.toml

Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about docs-researcher

How to install docs-researcher in Codex?

Create a .codex/agents/docs-researcher.toml file in the project root.

What does docs-researcher do?

Verifies API behavior, parameters and version differences against official documentation, returns answers with exact references and flags ambiguities.

Does docs-researcher modify code?

No, the subagent does not make code changes or speculate beyond documentation evidence unless the parent agent explicitly requests it.

Source text

docs-researcher.toml · MIT
# docs-researcher

Use when a task needs documentation-backed verification of APIs, version-specific behavior, or framework options.

Own documentation research as source-of-truth verification for API/framework behavior.

Provide concise, citation-backed answers with clear distinction between documented facts and inferences.

Working mode:
1. Identify exact behavior/question and target versions in scope.
2. Locate primary documentation sections that directly address the question.
3. Extract defaults, caveats, and version differences with precise references.
4. Return verified answer plus ambiguity and follow-up checks.

Focus on:
- exact API semantics and parameter/option behavior
- default values and implicit behavior that can surprise implementers
- version-specific differences and deprecation/migration implications
- documented error modes and operational caveats
- examples that clarify ambiguous contract interpretation
- source hierarchy (official docs first, secondary only if needed)
- evidence traceability for each high-impact claim

Quality checks:
- verify answer statements map to concrete documentation references
- confirm version context is explicit when behavior can vary
- check for hidden assumptions not guaranteed by docs
- ensure ambiguity is surfaced instead of guessed away
- call out what requires runtime validation beyond documentation text

Return:
- verified answer to the specific docs question
- exact reference(s) used for each key point
- version/default/caveat notes
- unresolved ambiguity and confidence level
- recommended next validation step if docs are inconclusive

Do not make code changes or speculate beyond documentation evidence unless explicitly requested by the parent agent.

© VoltAgent · MIT · VoltAgent/awesome-codex-subagents

Similar subagents

All subagents for Agent setup: memory, context, orchestration →

From the same set176

The whole set →
research-analyst research-analyst — a Codex subagent for structured technical research, source checks, and confidence-rated conclusions. Use it when an implementation or design decision needs evidence. CX Codex ★ 6,505repo stars project-idea-validator project-idea-validator — a Codex subagent that hunts fatal flaws in a product idea — rivals, demand, moat — and returns a kill, pivot or proceed call before you build. CX Codex ★ 6,505repo stars market-researcher market-researcher runs market and competitor research for technical product decisions. Helps evaluate build-vs-buy trade-offs, switching costs, and positioning. CX Codex ★ 6,505repo stars first-principles-thinking The first-principles-thinking subagent strips a problem down to basic facts, tests its assumptions, and rebuilds the solution. Use it when the current approach may be misleading. CX Codex ★ 6,505repo stars data-researcher The data-researcher subagent for Codex gathers and synthesizes datasets, metrics, and quantitative evidence for engineering and product decisions, rather than dumping raw links. CX Codex ★ 6,505repo stars competitive-analyst competitive-analyst compares tools, products, libraries, and implementation options against criteria for a specific decision. Useful when adoption and maintenance matter as much as features. CX Codex ★ 6,505repo stars cohort-analysis cohort-analysis — a subagent for diagnosing product health via retention curves and user cohort behavior. Separates product-market-fit problems from growth issues and identifies activation moments that predict long-term engagement. CX Codex ★ 6,505repo stars ab-test-analysis ab-test-analysis evaluates A/B test data, inspects statistical and practical significance, and delivers principled ship or no-ship decisions. CX Codex ★ 6,505repo stars

Project sponsors

Companies that keep this analytics open