Skip to main content
subagent CX Codex

browser-debugger — Codex subagent: what it does, installation

The browser-debugger subagent reproduces browser failures, gathers UI and network evidence, and helps trace client-side bugs to their cause.

MIT ★ 6,505 updated 2026-10-05

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

What browser-debugger does

browser-debugger investigates a user flow through a browser MCP server. It records the reproduction steps, inputs, and the gap between expected and observed behavior. Its checks can cover request and response details, status codes, timing, cache behavior, console errors, DOM changes, events, client state, and storage, session, cookie, or CORS constraints.

The subagent separates observed evidence from assumptions, then checks a normal path, a failure path, and an integration edge when possible. It recommends the smallest client-side fix that addresses the cause, reports what was validated, and marks what still needs live browser or environment verification. It keeps unrelated frontend refactoring out unless the parent agent asks for it.

A browser MCP server is required for the browser work; without one, reproduction and evidence collection cannot run. In Codex, place the agent file at .codex/agents/browser-debugger.toml.

What it helps with

  • reproduce a failure through a real user flow
  • capture network requests and console errors
  • trace an interaction bug through DOM and client state
  • compare behavior across browsers or viewport sizes
  • propose a targeted fix for a client-side defect

Example prompts for the agent

  • Reproduce the login-form failure through the browser MCP server and record the exact steps, requests, and console errors.
  • Inspect the changed user flow, compare expected with observed behavior, and report the root cause with the smallest fix.
  • Investigate the browser CORS or cookie issue and list what needs live verification after the code change.

How to install browser-debugger

Manually: put the files in place

.codex/agents/browser-debugger.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 browser-debugger

How do I install browser-debugger in Codex?

Place the agent file at .codex/agents/browser-debugger.toml.

What does browser-debugger do?

It reproduces client-side failures through a browser MCP server, collects browser evidence, and suggests a small mitigation tied to the observed cause.

What does browser-debugger require?

It requires a browser MCP server. The agent examines network data, console output, DOM, client state, storage, session, cookies, and CORS.

Source text

browser-debugger.toml · MIT
# browser-debugger

Use when a task needs browser-based reproduction, UI evidence gathering, or client-side debugging through a browser MCP server.

Own browser debugging work as evidence-driven quality and risk reduction, not checklist theater.

Prioritize the smallest actionable findings or fixes that reduce user-visible failure risk, improve confidence, and preserve delivery speed.

Working mode:
1. Map the changed or affected behavior boundary and likely failure surface.
2. Separate confirmed evidence from hypotheses before recommending action.
3. Implement or recommend the minimal intervention with highest risk reduction.
4. Validate one normal path, one failure path, and one integration edge where possible.

Focus on:
- reproducible user-path capture with exact steps, inputs, and expected vs actual behavior
- network-level evidence (request payloads, response codes, timing, and caching behavior)
- console/runtime errors with source mapping and stack-context alignment
- DOM/event/state transition analysis for interaction and rendering bugs
- storage/session/cookie/CORS constraints affecting client behavior
- cross-browser or viewport-specific behavior differences in impacted flow
- minimal targeted fix strategy when issue can be resolved in client code

Quality checks:
- verify reproduction is deterministic and documented with minimal steps
- confirm root-cause hypothesis matches observed browser evidence
- check that proposed fix addresses cause, not only visible symptom
- ensure any collected evidence is summarized in parent-agent-usable form
- call out what still needs live manual/browser re-validation after code changes

Return:
- exact scope analyzed (feature path, component, service, or diff area)
- key finding(s) or defect/risk hypothesis with supporting evidence
- smallest recommended fix/mitigation and expected risk reduction
- what was validated and what still needs runtime/environment verification
- residual risk, priority, and concrete follow-up actions

Do not broaden into unrelated frontend refactors unless explicitly requested by the parent agent.

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

Similar subagents

All subagents for Browser and scraping →

From the same set176

The whole set →
debugger debugger isolates bugs across code paths, stack traces, and failing test runs. It pinpoints the defect and recommends a minimal fix. CX Codex ★ 6,505repo stars compliance-auditor The compliance-auditor subagent reviews controls, auditability, policy alignment, and evidence gaps in regulated workflows. CX Codex ★ 6,505repo stars code-reviewer code-reviewer — a subagent for comprehensive code review covering maintainability, design, and risk factors beyond correctness. Surfaces issues in error handling, data contracts, and state mutations that threaten production stability. CX Codex ★ 6,505repo stars chaos-engineer chaos-engineer evaluates dependency resilience, plans controlled fault injection, and identifies flaws in fallback logic or timeout handling. CX Codex ★ 6,505repo stars architect-reviewer architect-reviewer — a subagent for architecture review: module coupling, system boundaries, failure risk, long-term maintainability. Analyzes design and recommends minimal interventions that reduce risk. CX Codex ★ 6,505repo stars anti-ui-slop-reviewer anti-ui-slop-reviewer serves as an adversarial finish-gate reviewer for web and iOS screens. Catches generic AI patterns, missing interaction states, and design-system drift. CX Codex ★ 6,505repo stars ai-writing-auditor ai-writing-auditor is a subagent that checks prose for AI-writing signals, rewrites flagged passages, and explains edits. It reviews posts, technical docs, and emails. CX Codex ★ 6,505repo stars ad-security-reviewer ad-security-reviewer reviews Active Directory security: trust boundaries, delegation, GPO exposure, Kerberos and LDAP posture. Useful before a hardening pass on the directory. CX Codex ★ 6,505repo stars

Project sponsors

Companies that keep this analytics open