testdriverai 6.0.16-canary.f0eefe0.0 → 6.0.16

package/agent/events.js

@@ -1,6 +1,7 @@
 const { EventEmitter2 } = require("eventemitter2");
+const { censorSensitiveDataDeep } = require("./lib/censorship");
 
-// Factory function to create a new emitter instance
+// Factory function to create a new emitter instance with censoring middleware
 const createEmitter = () => {
   const emitter = new EventEmitter2({
     wildcard: true,
@@ -11,6 +12,15 @@ const createEmitter = () => {
     verboseMemoryLeak: false,
     ignoreErrors: false,
   });
+
+  // Override emit to censor sensitive data before emitting
+  const originalEmit = emitter.emit.bind(emitter);
+  emitter.emit = function (event, ...args) {
+    // Censor all arguments passed to emit
+    const censoredArgs = args.map(censorSensitiveDataDeep);
+    return originalEmit(event, ...censoredArgs);
+  };
+
   return emitter;
 };
 

package/agent/index.js

@@ -1392,7 +1392,7 @@ ${regression}
         const mtime = new Date(stats.mtime);
         const now = new Date();
         const diffMinutes = (now - mtime) / (1000 * 60);
-        if (diffMinutes < 30) {
+        if (diffMinutes < 10) {
           const fileContent = fs.readFileSync(lastSandboxFile, "utf-8").trim();
 
           // Parse sandbox info (supports both old format and new format)
@@ -1465,8 +1465,8 @@ ${regression}
     // If instance already exists, do not build environment again
     if (this.instance) {
       this.emitter.emit(
-        events.log.log,
-        theme.dim("- sandbox instance already exists, skipping launch."),
+        events.log.narration,
+        theme.dim("sandbox instance already exists, skipping launch."),
       );
       return;
     }
@@ -1490,7 +1490,7 @@ ${regression}
       if (!this.config.CI) {
         this.emitter.emit(
           events.log.log,
-          theme.dim("-- `new` flag detected, will create a new sandbox"),
+          theme.dim("--`new` flag detected, will create a new sandbox"),
         );
       }
     }
@@ -1503,14 +1503,14 @@ ${regression}
     // Set sandbox ID for reconnection (only if not creating new and recent ID exists)
     if (!createNew && recentId) {
       this.emitter.emit(
-        events.log.log,
-        theme.dim(`- using recent sandbox: ${recentId}`),
+        events.log.narration,
+        theme.dim(`using recent sandbox: ${recentId}`),
       );
       this.sandboxId = recentId;
     } else if (!createNew) {
       this.emitter.emit(
-        events.log.log,
-        theme.dim(`- no recent sandbox found, creating a new one.`),
+        events.log.narration,
+        theme.dim(`no recent sandbox found, creating a new one.`),
       );
     }
 
@@ -1543,11 +1543,7 @@ ${regression}
 
     this.emitter.emit(
       events.log.narration,
-      theme.dim(`creating new sandbox...`),
-    );
-    this.emitter.emit(
-      events.log.log,
-      theme.dim(`this can take between 10 - 240 seconds`),
+      theme.dim(`creating new sandbox (can take up to 2 minutes)...`),
     );
     // We don't have resiliency/retries baked in, so let's at least give it 1 attempt
     // to see if that fixes the issue.

package/agent/lib/censorship.js

@@ -0,0 +1,70 @@
+// Shared censorship functionality for sensitive data
+// Uses @npmcli/redact for common patterns (URLs, auth headers, etc.)
+// Plus custom logic for environment variables and interpolation vars
+const { redactLog } = require("@npmcli/redact");
+
+let interpolationVars = JSON.parse(process.env.TD_INTERPOLATION_VARS || "{}");
+
+// Handle local `TD_*` variables
+for (const [key, value] of Object.entries(process.env)) {
+  if (key.startsWith("TD_") && key !== "TD_INTERPOLATION_VARS") {
+    interpolationVars[key] = value;
+  }
+}
+
+// Function to censor sensitive data in strings using both npmcli/redact and custom logic
+const censorSensitiveData = (message) => {
+  if (typeof message !== "string") {
+    return message;
+  }
+
+  // First, use npmcli/redact for common patterns:
+  // - URLs with credentials (https://user:pass@host)
+  // - Authorization headers
+  // - Common secret patterns in logs
+  let result = redactLog(message);
+
+  // Then apply our custom interpolation variable redaction
+  // This catches application-specific secrets from TD_* env vars
+  for (let value of Object.values(interpolationVars)) {
+    // Avoid replacing vars that are 0 or 1 characters
+    if (value && value.length >= 2) {
+      result = result.replaceAll(value, "****");
+    }
+  }
+
+  return result;
+};
+
+// Function to censor sensitive data in any value (recursive for objects/arrays)
+const censorSensitiveDataDeep = (value) => {
+  if (typeof value === "string") {
+    return censorSensitiveData(value);
+  } else if (Array.isArray(value)) {
+    return value.map(censorSensitiveDataDeep);
+  } else if (value && typeof value === "object") {
+    const result = {};
+    for (const [key, val] of Object.entries(value)) {
+      result[key] = censorSensitiveDataDeep(val);
+    }
+    return result;
+  }
+  return value;
+};
+
+// Function to update interpolation variables (for runtime updates)
+const updateInterpolationVars = (newVars) => {
+  interpolationVars = { ...interpolationVars, ...newVars };
+};
+
+// Function to get current interpolation variables (for debugging)
+const getInterpolationVars = () => {
+  return { ...interpolationVars };
+};
+
+module.exports = {
+  censorSensitiveData,
+  censorSensitiveDataDeep,
+  updateInterpolationVars,
+  getInterpolationVars,
+};

package/debugger/index.html

@@ -670,6 +670,8 @@
       // Handle window resize to recalculate scale (throttled)
       window.addEventListener("resize", throttle(resizeOverlay, 100));
 
+      setInterval(resizeOverlay, 1000);
+
       // Handle window blur/focus for screen locking
       window.addEventListener("blur", () => {
         showInteractionOverlay();

package/docs/_scripts/link-replacer.js

@@ -0,0 +1,164 @@
+#!/usr/bin/env node
+
+const fs = require("fs");
+const path = require("path");
+
+/**
+ * Script to replace command references in Mintlify docs with proper links
+ *
+ * This script finds instances of command names like `hover-text`, `wait-for-text`, etc.
+ * and replaces them with proper Mintlify links to their documentation pages.
+ */
+
+// Get all command files from the commands directory
+function getCommandNames() {
+  const commandsDir = path.join(__dirname, "../", "commands");
+
+  if (!fs.existsSync(commandsDir)) {
+    console.error("Commands directory not found:", commandsDir);
+    process.exit(1);
+  }
+
+  const files = fs.readdirSync(commandsDir);
+  const commands = files
+    .filter((file) => file.endsWith(".mdx"))
+    .map((file) => file.replace(".mdx", ""));
+
+  console.log("Found commands:", commands);
+  return commands;
+}
+
+// Process a single file
+function processFile(filePath, commands) {
+  const content = fs.readFileSync(filePath, "utf-8");
+  let modified = content;
+  let changes = 0;
+
+  commands.forEach((command) => {
+    // Create regex pattern to match `command-name` but not already linked commands
+    // This pattern looks for backtick-wrapped command names that are NOT:
+    // 1. Already inside a link: [` or preceded by ]( or ](/
+    // 2. Part of an existing link structure
+    const pattern = new RegExp(
+      `(?<!\\[)\`(${command.replace(/[-/\\^$*+?.()|[\]{}]/g, "\\$&")})\`(?!\\]\\(|\\)\\]|\\]\\(/commands/)`,
+      "g",
+    );
+
+    const replacement = `[\`$1\`](/commands/$1)`;
+    const newContent = modified.replace(pattern, replacement);
+
+    if (newContent !== modified) {
+      const matchCount = (modified.match(pattern) || []).length;
+      console.log(`  - Replaced ${matchCount} instances of \`${command}\``);
+      changes += matchCount;
+      modified = newContent;
+    }
+  });
+
+  return { content: modified, changes };
+}
+
+// Process all .mdx files in a directory recursively
+function processDirectory(dirPath, commands, exclude = []) {
+  const items = fs.readdirSync(dirPath);
+  let totalChanges = 0;
+
+  items.forEach((item) => {
+    const itemPath = path.join(dirPath, item);
+    const relativePath = path.relative(process.cwd(), itemPath);
+
+    // Skip excluded directories
+    if (exclude.some((ex) => relativePath.includes(ex))) {
+      return;
+    }
+
+    const stat = fs.statSync(itemPath);
+
+    if (stat.isDirectory()) {
+      totalChanges += processDirectory(itemPath, commands, exclude);
+    } else if (item.endsWith(".mdx")) {
+      console.log(`Processing: ${relativePath}`);
+      const result = processFile(itemPath, commands);
+
+      if (result.changes > 0) {
+        fs.writeFileSync(itemPath, result.content, "utf-8");
+        console.log(`  ✅ Updated with ${result.changes} changes`);
+        totalChanges += result.changes;
+      } else {
+        console.log(`  ⏭️  No changes needed`);
+      }
+    }
+  });
+
+  return totalChanges;
+}
+
+// Main function
+function main() {
+  console.log("🚀 Starting TestDriver AI docs link replacer...\n");
+
+  // Get command names from the commands directory
+  const commands = getCommandNames();
+
+  if (commands.length === 0) {
+    console.log("No commands found. Exiting.");
+    return;
+  }
+
+  console.log(`\n📝 Processing documentation files...\n`);
+
+  // Process all .mdx files in the docs directory, excluding the commands directory itself
+  const docsDir = path.join(__dirname, "../");
+  const exclude = ["commands"]; // Don't modify the command docs themselves
+
+  const totalChanges = processDirectory(docsDir, commands, exclude);
+
+  console.log(`\n✨ Complete! Made ${totalChanges} total replacements.`);
+
+  if (totalChanges > 0) {
+    console.log("\n📋 Summary:");
+    console.log(
+      "- Command references like `hover-text` have been replaced with [`hover-text`](/commands/hover-text)",
+    );
+    console.log("- Only changed files that needed updates");
+    console.log(
+      "- Excluded the /commands directory to avoid self-referencing issues",
+    );
+    console.log("\nYou may want to review the changes before committing.");
+  } else {
+    console.log("\n🎉 All files are already properly linked!");
+  }
+}
+
+// Handle command line arguments
+if (process.argv.includes("--help") || process.argv.includes("-h")) {
+  console.log(`
+TestDriver AI Documentation Link Replacer
+
+Usage: node link-replacer.js [options]
+
+Options:
+  --help, -h    Show this help message
+  --dry-run     Show what would be changed without making actual changes (TODO)
+
+Description:
+  This script finds command references like \`hover-text\` in your Mintlify 
+  documentation and replaces them with proper links to the command reference
+  pages like [\`hover-text\`](/commands/hover-text).
+
+  The script:
+  - Scans all .mdx files in the /docs directory
+  - Excludes the /commands directory to avoid self-references  
+  - Only replaces \`command-name\` patterns that aren't already linked
+  - Preserves existing links and formatting
+`);
+  process.exit(0);
+}
+
+// Run the script
+try {
+  main();
+} catch (error) {
+  console.error("❌ Error:", error.message);
+  process.exit(1);
+}

package/docs/account/dashboard.mdx

@@ -4,10 +4,13 @@ sidebarTitle: "Dashboard"
 description: "Explore your TestDriver dashboard and its features."
 icon: "gauge"
 ---
+
 ## Welcome to your TestDriver dashboard
+
 Your dashboard is your command center for managing your TestDriver experience. Here, you can view your projects, monitor usage, and access various features to enhance your testing workflow.
 
 ## Key features
+
 - **Projects**: Get a quick snapshot of your projects, with all Dashcam replays.
-- **Team**: Manage your API key, and add/remove team members. 
-- **Usage & Billing**: Monitor your usage and credits in real-time.
+- **Team**: Manage your API key, and add/remove team members.
+- **Usage & Billing**: Monitor your usage and credits in real-time.

package/docs/account/pricing.mdx

@@ -6,6 +6,7 @@ icon: "dollar-sign"
 ---
 
 ## TestDriver pricing plans
+
 TestDriver offers a range of pricing plans to suit different needs, from individual developers to large enterprises. Our plans are designed to provide flexibility and scalability, ensuring you can choose the right option for your testing requirements.
 
 <CardGroup cols={3}>
@@ -13,14 +14,20 @@ TestDriver offers a range of pricing plans to suit different needs, from individ
     Local agent testing. Always free.
   </Card>
   <Card title="Pro" icon="briefcase">
-    Use local or hosted runners on demand or integrated with CI for as low as $0.05/minute.
+    Use local or hosted runners on demand or integrated with CI for as low as
+    $0.05/minute.
   </Card>
-    <Card title="Enterprise" icon="shield">
-    Need advanced features? Contact us for tailored solutions. Starting at $995/month.
+  <Card title="Enterprise" icon="shield">
+    Need advanced features? Contact us for tailored solutions. Starting at
+    $995/month.
   </Card>
 </CardGroup>
 
-<Tip>Every plan starts with $100 in TestDriver credits to get you off the starting line!</Tip>
+<Tip>
+  Every plan starts with $100 in TestDriver credits to get you off the starting
+  line!
+</Tip>
 
 ## Compare plans
-To view the latest pricing and features, please visit our [Pricing Page](https://testdriver.ai/pricing).
+
+To view the latest pricing and features, please visit our [Pricing Page](https://testdriver.ai/pricing).

package/docs/account/projects.mdx

@@ -6,6 +6,7 @@ icon: "folder"
 ---
 
 ## Dashboard project view
+
 In the Project tab, select a Project to see the replays for that project.
 
 <Frame caption="Click a Project to view its replays">
@@ -18,10 +19,10 @@ From the Project view, you can see all the replays (Dashes) stored for that proj
   <img src="/images/content/account/projectreplays.png" />
 </Frame>
 
-
 ## New project
+
 When you create a new Project, you can also enable the <Icon icon="jira" /> Jira integration to create issues automatically each time a replay (Dash) is created.
 
 <Frame caption="Click a Project to view its replays">
   <img src="/images/content/account/newprojectsettings.png" />
-</Frame>
+</Frame>

package/docs/account/team.mdx

@@ -6,9 +6,11 @@ icon: "users"
 ---
 
 ## Important settings in one place
+
 In the Team tab, you can manage your team name, team members, API key, and subscription.
 
 ### Let's take a look at the team settings.
+
 <Frame caption="Team Settings">
   <img src="/images/content/account/teampage.png" />
 </Frame>
@@ -16,16 +18,18 @@ In the Team tab, you can manage your team name, team members, API key, and subsc
 1. **Team Name**: The name of your team. This is used to identify your team in TestDriver.
 2. **API Key**: Your API key is used to authenticate your requests to the TestDriver API. You can regenerate it if you suspect it has been compromised.
 3. **Usage & Billing**: Monitor your usage and billing information. This includes your current plan, usage limits, and billing history.
-<Tip>Note: this button is where you 'Upgrade to Pro' to start your free trial.</Tip>
+   <Tip>
+     Note: this button is where you 'Upgrade to Pro' to start your free trial.
+   </Tip>
 4. **Replay Visibility**: Toggle whether your replays are public or private by default. This defaults to **private**.
 5. **Don't forget to save your changes!**: After making any changes, be sure to click the **Update** button to apply them.
 
-
 ### Team members
+
 <Frame caption="Team Members">
   <img src="/images/content/account/team-manage.png" />
 </Frame>
 
 1. **Email Invite**: Invite new team members by entering their email address and clicking the **Invite** button. They will receive an email invitation to join your team. You can also copy the link above this option to send to everyone at once.
 2. **Removing Team Members**: To remove a team member, click the **Remove** button next to their name. This will revoke their access to your TestDriver account.
-3. **Invite Status**: The status of the invite will be shown here. If it says **Invited**, the invite hasn't been accepted yet. To resend it, click here.
+3. **Invite Status**: The status of the invite will be shown here. If it says **Invited**, the invite hasn't been accepted yet. To resend it, click here.

package/docs/apps/chrome-extensions.mdx

@@ -5,7 +5,7 @@ description: "Test Chrome extensions with TestDriver"
 icon: "puzzle-piece"
 ---
 
-import TestPrereqs from '/snippets/test-prereqs.mdx'
+import TestPrereqs from "/snippets/test-prereqs.mdx";
 
 <iframe
   width="600"
@@ -18,16 +18,21 @@ import TestPrereqs from '/snippets/test-prereqs.mdx'
 ></iframe>
 
 # Testing Chrome extensions with TestDriver
+
 TestDriver can be used to test Chrome extensions. This guide provides an overview of how to set up and run tests for your Chrome extension using TestDriver.
 
 <TestPrereqs />
 
 ## How do I test Chrome extensions?
+
 TestDriver provides a powerful solution for testing Chrome extensions. With our platform, you can easily create and run tests to ensure your extension functions as expected across different browsers and operating systems.
+
 ## Getting started
+
 You can test a preinstalled extension or test by installing an extension. If the extension is in development mode, turn this on by checking the "Developer mode" checkbox in the Chrome extensions page. From there you can load the unpacked extension by selecting the folder where your extension is located. To download the files onto the VM if you are performing a test on cloud hosted runners, see the [Lifecycle](/guide/lifecycle-prerun) and [Prerun](/action/pre-post-scripts) docs.
 
 ## Sample test steps
+
 1. Load a the Chrome Web Store.
 2. Search for the extension you want to test.
 3. Click on the extension to open its details page.
@@ -39,4 +44,5 @@ You can test a preinstalled extension or test by installing an extension. If the
 ---
 
 ## Now what?
-Once you have installed your extension, simply create a TestDriver test to test any functionality a user would use. 
+
+Once you have installed your extension, simply create a TestDriver test to test any functionality a user would use.

package/docs/apps/desktop-apps.mdx

@@ -24,11 +24,11 @@ TestDriver is designed to work with any desktop application, including Electron,
 
 ## Sample test steps
 
-1. **Launch the application**: Use the `exec` command to launch the application. You can specify the path to the executable file and any command-line arguments needed to start the application.
-2. **Wait for the application to load**: Use the `wait-for-text` command to wait for a specific text or element to appear in the application window. This ensures that the application is fully loaded before proceeding with the test.
-3. **Interact with the application**: Use the `focus-application` command to bring the application window to the foreground. Then, use the `hover-image` command to interact with specific elements in the application, such as buttons or text fields.
-4. **Perform actions**: Use the `hover-image` command to click on buttons or enter text in input fields. You can also use the `wait-for-text` command to verify that the expected output appears after performing an action.
-5. **Verify results**: Use the `assert` command to check if the expected result matches the actual output. This step is crucial for validating the functionality of the application.
+1. **Launch the application**: Use the [`exec`](/commands/exec) command to launch the application. You can specify the path to the executable file and any command-line arguments needed to start the application.
+2. **Wait for the application to load**: Use the [`wait-for-text`](/commands/wait-for-text) command to wait for a specific text or element to appear in the application window. This ensures that the application is fully loaded before proceeding with the test.
+3. **Interact with the application**: Use the [`focus-application`](/commands/focus-application) command to bring the application window to the foreground. Then, use the [`hover-image`](/commands/hover-image) command to interact with specific elements in the application, such as buttons or text fields.
+4. **Perform actions**: Use the [`hover-image`](/commands/hover-image) command to click on buttons or enter text in input fields. You can also use the [`wait-for-text`](/commands/wait-for-text) command to verify that the expected output appears after performing an action.
+5. **Verify results**: Use the [`assert`](/commands/assert) command to check if the expected result matches the actual output. This step is crucial for validating the functionality of the application.
 
 ## Supported desktop applications
 

package/docs/apps/mobile-apps.mdx

@@ -8,14 +8,19 @@ icon: "mobile"
 # Testing mobile apps with TestDriver
 
 ## How do I test mobile apps?
+
 TestDriver provides a powerful solution for testing mobile apps. With our platform, you can easily create and run tests to ensure your mobile app functions as expected across different devices and operating systems.
 
-<Tip>You will need to install a mobile emulator for your deployed tests or use a device farm to test your mobile app.</Tip>
+<Tip>
+  You will need to install a mobile emulator for your deployed tests or use a
+  device farm to test your mobile app.
+</Tip>
 
 ## Gettins started
+
 To get started with testing mobile apps using TestDriver, follow these steps:
+
 1. **Follow our [quick start guide](/overview/quickstart) to set up your TestDriver account.**
 2. **Create a new test project** in your TestDriver dashboard.
 3. **Add your mobile emulator to the test settings.**
 4. **Add your mobile app URL** to the test settings.
-

package/docs/cli/overview.mdx

@@ -15,11 +15,11 @@ npx testdriverai@latest <command> [options]
 
 ## Available commands
 
-| Command | Description                                                  |
-| ------- | ------------------------------------------------------------ |
-| `run`   | Executes a TestDriver test.                                  |
-| `edit`  | Launch interactive mode.                                     |
-| `help`  | Displays help information for the CLI or a specific command. |
+| Command                | Description                                                  |
+| ---------------------- | ------------------------------------------------------------ |
+| [`run`](/commands/run) | Executes a TestDriver test.                                  |
+| `edit`                 | Launch interactive mode.                                     |
+| `help`                 | Displays help information for the CLI or a specific command. |
 
 ## Available Flags
 
@@ -63,4 +63,4 @@ npx testdriverai@latest help <command>
 
 ## Protips
 
-- Combine `run` and `--headless` with CI/CD pipelines to automate test execution.
+- Combine [`run`](/commands/run) and `--headless` with CI/CD pipelines to automate test execution.

package/docs/commands/assert.mdx

@@ -6,20 +6,22 @@ icon: "check"
 mode: "wide"
 ---
 
-import Replay from '/snippets/tests/assert-replay.mdx'
-import Example from '/snippets/tests/assert-yaml.mdx'
+import Replay from "/snippets/tests/assert-replay.mdx";
+import Example from "/snippets/tests/assert-yaml.mdx";
 
 <Replay />
 <Example />
 
 ## Description
+
 The `assert` command validates that a specific condition is true. It ensures that a task completed successfully by checking the screen for the expected outcome. If the condition isn't met, the test will fail.
 
 ## Arguments
-| Argument   | Type      | Description                                                                 |
-|------------|-----------|-----------------------------------------------------------------------------|
-| `expect`   | `string`  | The condition to check. This should describe what you expect to see on the screen. |
-| `async`    | `boolean` | (Optional) If set to `true`, the test will continue without waiting for the assertion to pass. Default is `false`. |
+
+| Argument | Type      | Description                                                                                                        |
+| -------- | --------- | ------------------------------------------------------------------------------------------------------------------ |
+| `expect` | `string`  | The condition to check. This should describe what you expect to see on the screen.                                 |
+| `async`  | `boolean` | (Optional) If set to `true`, the test will continue without waiting for the assertion to pass. Default is `false`. |
 
 ## Example usage
 
@@ -37,5 +39,6 @@ async: true
 ```
 
 ## Notes
+
 - Use `async: true` to speed up tests by allowing non-blocking assertions. However, the test will still fail if the condition isn't met.
 - Ensure the `expect` string clearly describes the condition to avoid ambiguity.

package/docs/commands/hover-image.mdx

@@ -6,8 +6,8 @@ icon: "image"
 mode: "wide"
 ---
 
-import Replay from '/snippets/tests/hover-image-replay.mdx'
-import Example from '/snippets/tests/hover-image-yaml.mdx'
+import Replay from "/snippets/tests/hover-image-replay.mdx";
+import Example from "/snippets/tests/hover-image-yaml.mdx";
 
 <Replay />
 <Example />
@@ -17,14 +17,16 @@ import Example from '/snippets/tests/hover-image-yaml.mdx'
 The `hover-image` command is used to locate an image on the screen based on a description and perform an action on it. This can include hovering, clicking, right-clicking, or double-clicking the image.
 
 ## Arguments
-| Argument      | Type     | Description                                                                 |
-|---------------|----------|-----------------------------------------------------------------------------|
-| `description` | `string` | A description of the image and what it represents. Don't include the image itself here. |
+
+| Argument      | Type     | Description                                                                                                         |
+| ------------- | -------- | ------------------------------------------------------------------------------------------------------------------- |
+| `description` | `string` | A description of the image and what it represents. Don't include the image itself here.                             |
 | `action`      | `string` | The action to take when the image is found. Available actions are: `click`, `right-click`, `double-click`, `hover`. |
 
 The `hover-image` command is useful for interacting with visual elements that can't be identified using text-based selectors.
 
 ## Example usage
+
 ```yaml
 command: hover-image
 description: search icon in the webpage content
@@ -32,11 +34,12 @@ action: click
 ```
 
 ## Protips
+
 - Use clear and concise descriptions for the image to improve detection accuracy.
 - Ensure the action specified matches the intended interaction with the image.
 - If the hover-image command fails to locate an image based on the provided description, consider using the match-image command instead. The match-image command is specifically designed for scenarios where precise image matching is required, such as when the visual element can't be reliably described with text. It works by directly comparing the image on the screen with a reference image file.
 
 ## Gotchas
+
 - If the image can't be located based on the description, the command will fail.
 - Ensure the screen resolution and scaling settings are consistent to avoid detection issues.
-