qa-manual-tester — Claude Code subagent: manual browser QA
qa-manual-tester takes over a real browser and pokes at your app the way a tester would: clicks, typing, screenshots, console reads. Handy when a feature needs a hands-on pass.
no license ★ 406 updated 2026-06-25
.claude/agents/qa-manual-tester.mdWhat qa-manual-tester does
A Claude subagent that drives a real browser through your app. It navigates, clicks, fills fields, picks options from dropdowns, captures screenshots and reads the console, all via the Playwright MCP tools (mcp__playwright__browser_navigate, browser_click, browser_type, browser_screenshot and the rest). It does not write test suites. The job is a manual pass, carried out by an agent.
One markdown file, model: sonnet in the frontmatter, and a prompt that fixes the order of work. Flows and their expected outcomes come first, then smoke checks and happy paths, then boundary values and error states. Anything broken gets reproduced, captured in a screenshot and rated Critical, High, Medium or Low. Reports carry the steps taken, what was expected, what happened.
Without a Playwright MCP server connected there is nothing to test: the mcp__playwright__* tools simply aren't in the session, and you get a code review where you wanted a UI check. Set that up before the first run.
What it helps with
- check a sign-in form in the browser right after a change
- run a regression pass over checkout following a refactor
- reproduce a submit-button bug at a phone viewport
- get a severity-rated defect report with screenshots
- see what the console throws while a form submits
Example prompts for the agent
- Run qa-manual-tester and check whether the new sign-in form works.
- Have qa-manual-tester walk the whole checkout and note where it breaks.
- Send qa-manual-tester to the settings page at phone width and bring back screenshots of the errors.
How to install qa-manual-tester
Manually: put the files in place
.claude/agents/qa-manual-tester.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/qa-manual-tester.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/qa-manual-tester.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 qa-manual-tester
How do I install qa-manual-tester in Claude Code?
Drop the agent file at .claude/agents/qa-manual-tester.md inside your project, then call it by name.
What does qa-manual-tester do?
It drives a browser through the Playwright MCP tools: navigation, clicks, typing, screenshots, console output. You end up with a report on the defects it found and how serious each one is.
What does it need to run?
A connected Playwright MCP server, since without those tools it cannot open a page. The agent itself is set to model: sonnet.