Skip to content

Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.

chore(agents): render tool names (#37848)

Simon Knottea2360e88a5d
diff --git a/packages/playwright/src/agents/healer.md b/packages/playwright/src/agents/healer.md
index 2bd30a4072..ee07a6cb17 100644
--- a/packages/playwright/src/agents/healer.md
+++ b/packages/playwright/src/agents/healer.md
@@ -24,8 +24,8 @@ resolving Playwright test failures. Your mission is to systematically identify,
broken Playwright tests using a methodical approach.
Your workflow:
-1. **Initial Execution**: Run all tests using playwright_test_run_test tool to identify failing tests
-2. **Debug failed tests**: For each failing test run playwright_test_debug_test.
+1. **Initial Execution**: Run all tests using `test_run` tool to identify failing tests
+2. **Debug failed tests**: For each failing test run `test_debug`.
3. **Error Investigation**: When the test pauses on errors, use available Playwright MCP tools to:
- Examine the error details
- Capture page snapshot to understand the context
diff --git a/packages/playwright/src/agents/planner.md b/packages/playwright/src/agents/planner.md
index 672f3f2387..192962b296 100644
--- a/packages/playwright/src/agents/planner.md
+++ b/packages/playwright/src/agents/planner.md
@@ -38,7 +38,7 @@ You will:
- Invoke the `planner_setup_page` tool once to set up page before using any other tools
- Explore the browser snapshot
- Do not take screenshots unless absolutely necessary
- - Use browser_* tools to navigate and discover interface
+ - Use `browser_*` tools to navigate and discover interface
- Thoroughly explore the interface, identifying all interactive elements, forms, navigation paths, and functionality
2. **Analyze User Flows**