@testdriverai/mcp 7.11.221-test → 7.11.222-canary

package/ai/agents/testdriver.md

@@ -44,7 +44,7 @@ Use this agent when the user asks to:
 4. **⚠️ WRITE CODE IMMEDIATELY**: After EVERY successful action, append the generated code to the test file RIGHT AWAY. Do NOT wait until the end.
 5. **Verify Actions**: Use `check` after actions to verify they succeeded (for YOUR understanding only).
 6. **Add Assertions**: Use `assert` for test conditions that should be in the final test file.
-7. **⚠️ RUN THE TEST YOURSELF**: Use `vitest run <testFile>` to run the test - do NOT tell the user to run it. Iterate until it passes. **NEVER use `npx vitest`** - always use `vitest` directly.
+7. **⚠️ RUN THE TEST YOURSELF**: Use `vitest run` to run the test - do NOT tell the user to run it. Iterate until it passes.
 8. **⚠️ SHARE THE TEST REPORT**: After EVERY test run, find the `TESTDRIVER_RUN_URL` in the output (e.g., `TESTDRIVER_RUN_URL=https://console.testdriver.ai/runs/...`) and share it with the user so they can view the recording and results.
 
 ## Prerequisites
@@ -255,7 +255,7 @@ TestDriver **automatically captures screenshots before and after every command**
 
 **Every MCP tool response includes "ACTION REQUIRED: Append this code..." - you MUST write that code to the test file IMMEDIATELY before proceeding to the next action.**
 
-**When ready to validate, RUN THE TEST YOURSELF using `vitest run`. Do NOT tell the user to run it. NEVER use `npx vitest`.**
+**When ready to validate, RUN THE TEST YOURSELF using `vitest run`. Do NOT tell the user to run it.**
 
 ### Step 1: Start a Session
 
@@ -312,7 +312,7 @@ assert({ assertion: "the dashboard is visible" })
 
 ### Step 5: Run the Test Yourself
 
-**⚠️ YOU must run the test - do NOT tell the user to run it. NEVER use `npx vitest` - always use `vitest` directly:**
+**⚠️ YOU must run the test - do NOT tell the user to run it. Use `vitest run`:**
 
 ```bash
 vitest run tests/login.test.mjs
@@ -455,7 +455,7 @@ list_local_screenshots({ directory: "checkout.test", phase: "before", limit: 10
 ### Tips for MCP Workflow
 
 1. **⚠️ Write code IMMEDIATELY** - After EVERY action, append generated code to test file RIGHT AWAY
-2. **⚠️ Run tests YOURSELF** - Use `vitest run` (NEVER `npx vitest`) - do NOT tell user to run tests
+2. **⚠️ Run tests YOURSELF** - Use `vitest run` - do NOT tell user to run tests
 3. **⚠️ Add screenshots liberally** - Include `await testdriver.screenshot()` after every significant action for debugging
 4. **⚠️ Use screenshot viewing for debugging** - When tests fail, use `list_local_screenshots` and `view_local_screenshot` to understand what went wrong
 5. **Work incrementally** - Don't try to build the entire test at once
@@ -610,7 +610,7 @@ await testdriver.screenshot(1, false, true);
 ## Tips for Agents
 
 1. **⚠️ WRITE CODE IMMEDIATELY** - After EVERY successful MCP action, append the generated code to the test file RIGHT AWAY. Do NOT wait until the session ends.
-2. **⚠️ RUN TESTS YOURSELF** - Do NOT tell the user to run tests. YOU must run the tests using `vitest run <testFile>` (NEVER use `npx vitest`). Analyze the output and iterate until the test passes.
+2. **⚠️ RUN TESTS YOURSELF** - Do NOT tell the user to run tests. YOU must run the tests using `vitest run <testFile>`. Analyze the output and iterate until the test passes.
 3. **⚠️ SHARE THE TEST REPORT URL** - After EVERY test run, find `TESTDRIVER_RUN_URL=https://console.testdriver.ai/runs/...` in the output and share it with the user. This is CRITICAL - users need to view the recording to understand what happened.
 3. **Screenshots are automatic** - TestDriver captures screenshots before/after every command by default. Each screenshot filename includes the line number (e.g., `001-click-before-L42-submit-button.png`) making it easy to trace issues.
 4. **⚠️ USE SCREENSHOT VIEWING FOR DEBUGGING** - When tests fail, use `list_local_screenshots` and `view_local_screenshot` MCP commands to see exactly what the UI looked like. The filenames tell you which line of code triggered each screenshot.

package/ai/skills/testdriver-aws-setup/SKILL.md

@@ -256,7 +256,7 @@ jobs:
         run: npm ci
 
       - name: Run Windows tests with self-hosted instances
-        run: npx vitest run examples/*.test.mjs
+        run: vitest run examples/*.test.mjs
         env:
           TD_API_KEY: ${{ secrets.TD_API_KEY }}
           TD_OS: windows

package/ai/skills/testdriver-cache/SKILL.md

@@ -93,7 +93,7 @@ const testdriver = new TestDriver({
 const testdriver = new TestDriver({ cache: false });
 
 // Via environment variable
-// TD_NO_CACHE=true npx vitest run
+// TD_NO_CACHE=true vitest run
 ```
 
 When cache is disabled, all thresholds are set to `-1` internally, causing the API to skip cache lookups.

package/ai/skills/testdriver-ci-cd/SKILL.md

@@ -65,7 +65,7 @@ Add it as a `TD_API_KEY` secret in the settings of your CI provider.
               api-key: ${{ secrets.TD_API_KEY }}   # optional fallback if OIDC isn't set up
 
           - name: Run TestDriver tests
-            run: npx vitest run
+            run: vitest run
     ```
 
     ### Stored-key fallback
@@ -664,7 +664,7 @@ and the realtime slot-approval handshake.
   env:
     TD_API_KEY: ${{ secrets.TD_API_KEY }}
     TD_CONCURRENCY_MAX_WAIT: "300"
-  run: npx vitest run
+  run: vitest run
 ```
 
 <Tip>

package/ai/skills/testdriver-quickstart-manual/SKILL.md

@@ -104,7 +104,7 @@ If you only want to drive TestDriver from chat, [MCP Setup](/mcp-setup) is a sin
   <Step title="Run the test">
 
     ```bash
-    npx vitest run
+    vitest run
     ```
 
     A sandbox starts, Chrome opens, and a live preview appears in your browser. When the run finishes, open the `TESTDRIVER_RUN_URL` printed at the end of the output to see the recording and step-by-step screenshots.

package/ai/skills/testdriver-test-results-json/SKILL.md

@@ -175,7 +175,7 @@ Use `fromJSON` to parse a result file into a GitHub Actions expression you can r
 
 ```yaml
 - name: Run tests
-  run: npx vitest run tests/login.test.mjs
+  run: vitest run tests/login.test.mjs
 
 - name: Parse result
   id: result
@@ -210,7 +210,7 @@ You can also load all results into a matrix or iterate over them:
 
 ```yaml
 - name: Run tests
-  run: npx vitest run tests/*.test.mjs
+  run: vitest run tests/*.test.mjs
 
 - name: Collect results
   id: results

package/ai/skills/testdriver-testdriver/SKILL.md

@@ -34,7 +34,7 @@ Use this agent when the user asks to:
 4. **⚠️ WRITE CODE IMMEDIATELY**: After EVERY successful action, append the generated code to the test file RIGHT AWAY. Do NOT wait until the end.
 5. **Verify Actions**: Use `check` after actions to verify they succeeded (for YOUR understanding only).
 6. **Add Assertions**: Use `assert` for test conditions that should be in the final test file.
-7. **⚠️ RUN THE TEST YOURSELF**: Use `vitest run <testFile>` to run the test - do NOT tell the user to run it. Iterate until it passes. **NEVER use `npx vitest`** - always use `vitest` directly.
+7. **⚠️ RUN THE TEST YOURSELF**: Use `vitest run` to run the test - do NOT tell the user to run it. Iterate until it passes.
 8. **⚠️ SHARE THE TEST REPORT**: After EVERY test run, find the `TESTDRIVER_RUN_URL` in the output (e.g., `TESTDRIVER_RUN_URL=https://console.testdriver.ai/runs/...`) and share it with the user so they can view the recording and results.
 
 ## Prerequisites
@@ -245,7 +245,7 @@ TestDriver **automatically captures screenshots before and after every command**
 
 **Every MCP tool response includes "ACTION REQUIRED: Append this code..." - you MUST write that code to the test file IMMEDIATELY before proceeding to the next action.**
 
-**When ready to validate, RUN THE TEST YOURSELF using `vitest run`. Do NOT tell the user to run it. NEVER use `npx vitest`.**
+**When ready to validate, RUN THE TEST YOURSELF using `vitest run`. Do NOT tell the user to run it.**
 
 ### Step 1: Start a Session
 
@@ -302,7 +302,7 @@ assert({ assertion: "the dashboard is visible" })
 
 ### Step 5: Run the Test Yourself
 
-**⚠️ YOU must run the test - do NOT tell the user to run it. NEVER use `npx vitest` - always use `vitest` directly:**
+**⚠️ YOU must run the test - do NOT tell the user to run it. Use `vitest run`:**
 
 ```bash
 vitest run tests/login.test.mjs
@@ -445,7 +445,7 @@ list_local_screenshots({ directory: "checkout.test", phase: "before", limit: 10
 ### Tips for MCP Workflow
 
 1. **⚠️ Write code IMMEDIATELY** - After EVERY action, append generated code to test file RIGHT AWAY
-2. **⚠️ Run tests YOURSELF** - Use `vitest run` (NEVER `npx vitest`) - do NOT tell user to run tests
+2. **⚠️ Run tests YOURSELF** - Use `vitest run` - do NOT tell user to run tests
 3. **⚠️ Add screenshots liberally** - Include `await testdriver.screenshot()` after every significant action for debugging
 4. **⚠️ Use screenshot viewing for debugging** - When tests fail, use `list_local_screenshots` and `view_local_screenshot` to understand what went wrong
 5. **Work incrementally** - Don't try to build the entire test at once
@@ -600,7 +600,7 @@ await testdriver.screenshot(1, false, true);
 ## Tips for Agents
 
 1. **⚠️ WRITE CODE IMMEDIATELY** - After EVERY successful MCP action, append the generated code to the test file RIGHT AWAY. Do NOT wait until the session ends.
-2. **⚠️ RUN TESTS YOURSELF** - Do NOT tell the user to run tests. YOU must run the tests using `vitest run <testFile>` (NEVER use `npx vitest`). Analyze the output and iterate until the test passes.
+2. **⚠️ RUN TESTS YOURSELF** - Do NOT tell the user to run tests. YOU must run the tests using `vitest run <testFile>`. Analyze the output and iterate until the test passes.
 3. **⚠️ SHARE THE TEST REPORT URL** - After EVERY test run, find `TESTDRIVER_RUN_URL=https://console.testdriver.ai/runs/...` in the output and share it with the user. This is CRITICAL - users need to view the recording to understand what happened.
 3. **Screenshots are automatic** - TestDriver captures screenshots before/after every command by default. Each screenshot filename includes the line number (e.g., `001-click-before-L42-submit-button.png`) making it easy to trace issues.
 4. **⚠️ USE SCREENSHOT VIEWING FOR DEBUGGING** - When tests fail, use `list_local_screenshots` and `view_local_screenshot` MCP commands to see exactly what the UI looked like. The filenames tell you which line of code triggered each screenshot.

package/ai/skills/testdriver:aws-setup/SKILL.md

@@ -256,7 +256,7 @@ jobs:
         run: npm ci
 
       - name: Run Windows tests with self-hosted instances
-        run: npx vitest run examples/*.test.mjs
+        run: vitest run examples/*.test.mjs
         env:
           TD_API_KEY: ${{ secrets.TD_API_KEY }}
           TD_OS: windows

package/ai/skills/testdriver:cache/SKILL.md

@@ -93,7 +93,7 @@ const testdriver = new TestDriver({
 const testdriver = new TestDriver({ cache: false });
 
 // Via environment variable
-// TD_NO_CACHE=true npx vitest run
+// TD_NO_CACHE=true vitest run
 ```
 
 When cache is disabled, all thresholds are set to `-1` internally, causing the API to skip cache lookups.

package/ai/skills/testdriver:test-results-json/SKILL.md

@@ -175,7 +175,7 @@ Use `fromJSON` to parse a result file into a GitHub Actions expression you can r
 
 ```yaml
 - name: Run tests
-  run: npx vitest run tests/login.test.mjs
+  run: vitest run tests/login.test.mjs
 
 - name: Parse result
   id: result
@@ -210,7 +210,7 @@ You can also load all results into a matrix or iterate over them:
 
 ```yaml
 - name: Run tests
-  run: npx vitest run tests/*.test.mjs
+  run: vitest run tests/*.test.mjs
 
 - name: Collect results
   id: results

package/ai/skills/testdriver:testdriver/SKILL.md

@@ -34,7 +34,7 @@ Use this agent when the user asks to:
 4. **⚠️ WRITE CODE IMMEDIATELY**: After EVERY successful action, append the generated code to the test file RIGHT AWAY. Do NOT wait until the end.
 5. **Verify Actions**: Use `check` after actions to verify they succeeded (for YOUR understanding only).
 6. **Add Assertions**: Use `assert` for test conditions that should be in the final test file.
-7. **⚠️ RUN THE TEST YOURSELF**: Use `vitest run <testFile>` to run the test - do NOT tell the user to run it. Iterate until it passes. **NEVER use `npx vitest`** - always use `vitest` directly.
+7. **⚠️ RUN THE TEST YOURSELF**: Use `vitest run` to run the test - do NOT tell the user to run it. Iterate until it passes.
 8. **⚠️ SHARE THE TEST REPORT**: After EVERY test run, find the `TESTDRIVER_RUN_URL` in the output (e.g., `TESTDRIVER_RUN_URL=https://console.testdriver.ai/runs/...`) and share it with the user so they can view the recording and results.
 
 ## Prerequisites
@@ -245,7 +245,7 @@ TestDriver **automatically captures screenshots before and after every command**
 
 **Every MCP tool response includes "ACTION REQUIRED: Append this code..." - you MUST write that code to the test file IMMEDIATELY before proceeding to the next action.**
 
-**When ready to validate, RUN THE TEST YOURSELF using `vitest run`. Do NOT tell the user to run it. NEVER use `npx vitest`.**
+**When ready to validate, RUN THE TEST YOURSELF using `vitest run`. Do NOT tell the user to run it.**
 
 ### Step 1: Start a Session
 
@@ -302,7 +302,7 @@ assert({ assertion: "the dashboard is visible" })
 
 ### Step 5: Run the Test Yourself
 
-**⚠️ YOU must run the test - do NOT tell the user to run it. NEVER use `npx vitest` - always use `vitest` directly:**
+**⚠️ YOU must run the test - do NOT tell the user to run it. Use `vitest run`:**
 
 ```bash
 vitest run tests/login.test.mjs
@@ -445,7 +445,7 @@ list_local_screenshots({ directory: "checkout.test", phase: "before", limit: 10
 ### Tips for MCP Workflow
 
 1. **⚠️ Write code IMMEDIATELY** - After EVERY action, append generated code to test file RIGHT AWAY
-2. **⚠️ Run tests YOURSELF** - Use `vitest run` (NEVER `npx vitest`) - do NOT tell user to run tests
+2. **⚠️ Run tests YOURSELF** - Use `vitest run` - do NOT tell user to run tests
 3. **⚠️ Add screenshots liberally** - Include `await testdriver.screenshot()` after every significant action for debugging
 4. **⚠️ Use screenshot viewing for debugging** - When tests fail, use `list_local_screenshots` and `view_local_screenshot` to understand what went wrong
 5. **Work incrementally** - Don't try to build the entire test at once
@@ -600,7 +600,7 @@ await testdriver.screenshot(1, false, true);
 ## Tips for Agents
 
 1. **⚠️ WRITE CODE IMMEDIATELY** - After EVERY successful MCP action, append the generated code to the test file RIGHT AWAY. Do NOT wait until the session ends.
-2. **⚠️ RUN TESTS YOURSELF** - Do NOT tell the user to run tests. YOU must run the tests using `vitest run <testFile>` (NEVER use `npx vitest`). Analyze the output and iterate until the test passes.
+2. **⚠️ RUN TESTS YOURSELF** - Do NOT tell the user to run tests. YOU must run the tests using `vitest run <testFile>`. Analyze the output and iterate until the test passes.
 3. **⚠️ SHARE THE TEST REPORT URL** - After EVERY test run, find `TESTDRIVER_RUN_URL=https://console.testdriver.ai/runs/...` in the output and share it with the user. This is CRITICAL - users need to view the recording to understand what happened.
 3. **Screenshots are automatic** - TestDriver captures screenshots before/after every command by default. Each screenshot filename includes the line number (e.g., `001-click-before-L42-submit-button.png`) making it easy to trace issues.
 4. **⚠️ USE SCREENSHOT VIEWING FOR DEBUGGING** - When tests fail, use `list_local_screenshots` and `view_local_screenshot` MCP commands to see exactly what the UI looked like. The filenames tell you which line of code triggered each screenshot.

package/docs/_scripts/generate-examples.js

@@ -447,7 +447,7 @@ cd testdriverai
 npm install
 
 # Run this specific example
-npx vitest run examples/${testMeta.filename}
+vitest run examples/${testMeta.filename}
 \`\`\`
 
 <Note>

package/docs/aws-setup.mdx

@@ -257,7 +257,7 @@ jobs:
         run: npm ci
 
       - name: Run Windows tests with self-hosted instances
-        run: npx vitest run examples/*.test.mjs
+        run: vitest run examples/*.test.mjs
         env:
           TD_API_KEY: ${{ secrets.TD_API_KEY }}
           TD_OS: windows

package/docs/cache.mdx

@@ -95,7 +95,7 @@ const testdriver = new TestDriver({
 const testdriver = new TestDriver({ cache: false });
 
 // Via environment variable
-// TD_NO_CACHE=true npx vitest run
+// TD_NO_CACHE=true vitest run
 ```
 
 When cache is disabled, all thresholds are set to `-1` internally, causing the API to skip cache lookups.

package/docs/ci-cd.mdx

@@ -66,7 +66,7 @@ Add it as a `TD_API_KEY` secret in the settings of your CI provider.
               api-key: ${{ secrets.TD_API_KEY }}   # optional fallback if OIDC isn't set up
 
           - name: Run TestDriver tests
-            run: npx vitest run
+            run: vitest run
     ```
 
     ### Stored-key fallback
@@ -665,7 +665,7 @@ and the realtime slot-approval handshake.
   env:
     TD_API_KEY: ${{ secrets.TD_API_KEY }}
     TD_CONCURRENCY_MAX_WAIT: "300"
-  run: npx vitest run
+  run: vitest run
 ```
 
 <Tip>

package/docs/examples/ai.mdx

@@ -70,7 +70,7 @@ cd testdriverai
 npm install
 
 # Run this specific example
-npx vitest run examples/ai.test.mjs
+vitest run examples/ai.test.mjs
 ```
 
 <Note>

package/docs/examples/assert.mdx

@@ -79,7 +79,7 @@ cd testdriverai
 npm install
 
 # Run this specific example
-npx vitest run examples/assert.test.mjs
+vitest run examples/assert.test.mjs
 ```
 
 <Note>

package/docs/examples/captcha-api.mdx

@@ -84,7 +84,7 @@ cd testdriverai
 npm install
 
 # Run this specific example
-npx vitest run examples/captcha-api.test.mjs
+vitest run examples/captcha-api.test.mjs
 ```
 
 <Note>

package/docs/examples/chrome-extension.mdx

@@ -148,7 +148,7 @@ cd testdriverai
 npm install
 
 # Run this specific example
-npx vitest run examples/chrome-extension.test.mjs
+vitest run examples/chrome-extension.test.mjs
 ```
 
 <Note>

package/docs/examples/drag-and-drop.mdx

@@ -92,7 +92,7 @@ cd testdriverai
 npm install
 
 # Run this specific example
-npx vitest run examples/drag-and-drop.test.mjs
+vitest run examples/drag-and-drop.test.mjs
 ```
 
 <Note>

package/docs/examples/element-not-found.mdx

@@ -60,7 +60,7 @@ cd testdriverai
 npm install
 
 # Run this specific example
-npx vitest run examples/element-not-found.test.mjs
+vitest run examples/element-not-found.test.mjs
 ```
 
 <Note>

package/docs/examples/findall-coffee-icons.mdx

@@ -81,7 +81,7 @@ cd testdriverai
 npm install
 
 # Run this specific example
-npx vitest run examples/findall-coffee-icons.test.mjs
+vitest run examples/findall-coffee-icons.test.mjs
 ```
 
 <Note>

package/docs/examples/formatted-logging.mdx

@@ -66,7 +66,7 @@ cd testdriverai
 npm install
 
 # Run this specific example
-npx vitest run examples/formatted-logging.test.mjs
+vitest run examples/formatted-logging.test.mjs
 ```
 
 <Note>

package/docs/examples/hover-image.mdx

@@ -87,7 +87,7 @@ cd testdriverai
 npm install
 
 # Run this specific example
-npx vitest run examples/hover-image.test.mjs
+vitest run examples/hover-image.test.mjs
 ```
 
 <Note>

package/docs/examples/hover-text-with-description.mdx

@@ -96,7 +96,7 @@ cd testdriverai
 npm install
 
 # Run this specific example
-npx vitest run examples/hover-text-with-description.test.mjs
+vitest run examples/hover-text-with-description.test.mjs
 ```
 
 <Note>

package/docs/examples/hover-text.mdx

@@ -62,7 +62,7 @@ cd testdriverai
 npm install
 
 # Run this specific example
-npx vitest run examples/hover-text.test.mjs
+vitest run examples/hover-text.test.mjs
 ```
 
 <Note>

package/docs/examples/installer.mdx

@@ -84,7 +84,7 @@ cd testdriverai
 npm install
 
 # Run this specific example
-npx vitest run examples/installer.test.mjs
+vitest run examples/installer.test.mjs
 ```
 
 <Note>

package/docs/examples/launch-vscode-linux.mdx

@@ -89,7 +89,7 @@ cd testdriverai
 npm install
 
 # Run this specific example
-npx vitest run examples/launch-vscode-linux.test.mjs
+vitest run examples/launch-vscode-linux.test.mjs
 ```
 
 <Note>

package/docs/examples/match-image.mdx

@@ -89,7 +89,7 @@ cd testdriverai
 npm install
 
 # Run this specific example
-npx vitest run examples/match-image.test.mjs
+vitest run examples/match-image.test.mjs
 ```
 
 <Note>

package/docs/examples/parse.mdx

@@ -59,7 +59,7 @@ cd testdriverai
 npm install
 
 # Run this specific example
-npx vitest run examples/parse.test.mjs
+vitest run examples/parse.test.mjs
 ```
 
 <Note>

package/docs/examples/press-keys.mdx

@@ -78,7 +78,7 @@ cd testdriverai
 npm install
 
 # Run this specific example
-npx vitest run examples/press-keys.test.mjs
+vitest run examples/press-keys.test.mjs
 ```
 
 <Note>

package/docs/examples/scroll-keyboard.mdx

@@ -72,7 +72,7 @@ cd testdriverai
 npm install
 
 # Run this specific example
-npx vitest run examples/scroll-keyboard.test.mjs
+vitest run examples/scroll-keyboard.test.mjs
 ```
 
 <Note>

package/docs/examples/scroll-until-text.mdx

@@ -101,7 +101,7 @@ cd testdriverai
 npm install
 
 # Run this specific example
-npx vitest run examples/scroll-until-text.test.mjs
+vitest run examples/scroll-until-text.test.mjs
 ```
 
 <Note>

package/docs/examples/scroll.mdx

@@ -65,7 +65,7 @@ cd testdriverai
 npm install
 
 # Run this specific example
-npx vitest run examples/scroll.test.mjs
+vitest run examples/scroll.test.mjs
 ```
 
 <Note>

package/docs/examples/type.mdx

@@ -80,7 +80,7 @@ cd testdriverai
 npm install
 
 # Run this specific example
-npx vitest run examples/type.test.mjs
+vitest run examples/type.test.mjs
 ```
 
 <Note>

package/docs/quickstart-manual.mdx

@@ -105,7 +105,7 @@ If you only want to drive TestDriver from chat, [MCP Setup](/mcp-setup) is a sin
   <Step title="Run the test">
 
     ```bash
-    npx vitest run
+    vitest run
     ```
 
     A sandbox starts, Chrome opens, and a live preview appears in your browser. When the run finishes, open the `TESTDRIVER_RUN_URL` printed at the end of the output to see the recording and step-by-step screenshots.

package/docs/test-results-json.mdx

@@ -176,7 +176,7 @@ Use `fromJSON` to parse a result file into a GitHub Actions expression you can r
 
 ```yaml
 - name: Run tests
-  run: npx vitest run tests/login.test.mjs
+  run: vitest run tests/login.test.mjs
 
 - name: Parse result
   id: result
@@ -211,7 +211,7 @@ You can also load all results into a matrix or iterate over them:
 
 ```yaml
 - name: Run tests
-  run: npx vitest run tests/*.test.mjs
+  run: vitest run tests/*.test.mjs
 
 - name: Collect results
   id: results

package/lib/init-project.js

@@ -289,7 +289,7 @@ jobs:
         api-key: \${{ secrets.TD_API_KEY }}
 
     - name: Run TestDriver.ai tests
-      run: npx vitest run
+      run: vitest run
 
     - name: Upload test results
       if: always()

package/manual/packer-hover-image.test.mjs

@@ -8,7 +8,7 @@
  * Usage:
  *   TD_API_ROOT=http://localhost:1337 \
  *   TD_API_KEY=<key> \
- *   npx vitest run examples/packer-hover-image.test.mjs
+ *   vitest run examples/packer-hover-image.test.mjs
  *
  * The packer build takes ~25 minutes, and the hover-image test ~5-10 minutes,
  * so the overall test timeout is set to 60 minutes.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@testdriverai/mcp",
-  "version": "7.11.221-test",
+  "version": "7.11.222-canary",
   "description": "Next generation autonomous AI agent for end-to-end testing of web & desktop",
   "main": "sdk.js",
   "types": "sdk.d.ts",