[Feature]: When will the Playwright test agent support Cursor?

[zh199609]

🚀 Feature Request

When will the Playwright test agent support Cursor?

Example

No response

Motivation

./cursor/agents

[github-actions]

Hi, I'm the Playwright bot and I took a first look at this.

Valid feature request — Cursor isn't a supported loop today. The test agent is scaffolded by npx playwright init-agents --loop <provider>, and on tip-of-tree (1.62.0-next) the --loop choices are claude, codex, copilot, opencode, vscode, and vscode-legacy. There's no cursor generator, so there's nothing that writes .cursor/agents (or a .cursor/mcp.json) for you.

Worth separating two things, since "Cursor support" can mean either:

• The browser MCP (@playwright/mcp) already works in Cursor — it's a standard MCP client. See the Getting started with MCP docs.
• The test agent (init-agents) is what's missing a Cursor target — that's this request.

Where this lives in the source

• CLI wiring: packages/playwright/src/program.ts — init-agents command, --loop choices ['claude', 'codex', 'copilot', 'opencode', 'vscode', 'vscode-legacy'].
• Generators: packages/playwright/src/agents/generateAgents.ts — ClaudeGenerator, CodexGenerator, OpencodeGenerator, CopilotGenerator, VSCodeGenerator. Adding Cursor would mean a CursorGenerator writing to Cursor's agent/MCP config layout plus a new --loop cursor choice.

One question to scope it: which Cursor surface are you after — subagents under .cursor/agents, or just the MCP server wired into .cursor/mcp.json? That decides how much a Cursor generator needs to emit.

_{Triage run}

[Skn0tt]

Hi! Let's wait for more upvotes on this issue. As far as I understand, manually converting one of the existing outputs into what Cursor wants is straight-forward as a workaround.