testdriverai 6.1.10 → 6.2.0

package/docs/account/enterprise.mdx

@@ -24,15 +24,15 @@ We specialize in testing scenarios that other tools can't handle - desktop appli
 
 ## Enterprise Plans
 
-TestDriver Enterprise plans start at **$2,000/month** and include:
+TestDriver Enterprise plans start at **$995/month** and include:
 
-- A pilot program with our expert team to create 4 custom tests within your first 4 weeks (4x4 Guarantee).
-- 4 parallel tests
 - **12,500 runner minutes per month**: Sufficient capacity for continuous testing of your custom test suite.
+- Enterprise-grade test dashboards with advanced analytics.
 - Full CI/CD pipeline integration with custom configurations.
 - Dedicated infrastructure and ongoing support for complex testing scenarios.
+- Expert test creation and maintenance services.
 
-For detailed pricing and contract information our [Pricing](/account/pricing) page. Want unlimited minutes or enhanced security? We also support self-hosted options with 16 parallel tests starting at $2,000/month. See our [Self Hosting](/getting-started/self-hosting) docs for more info.
+For detailed pricing and contract information, see [Contract Details](#contract-details). For other plans, visit our [Pricing](/account/pricing) page.
 
 <CardGroup cols={3}>
   <Card title="Custom Desktop & Extension Testing">
@@ -66,14 +66,17 @@ TestDriver Enterprise provides comprehensive support for fast-moving teams with
 
 Testing complex applications requires more than standard automation tools. Desktop applications, browser extensions, and multi-platform workflows demand specialized infrastructure, custom integrations, and deep technical expertise. TestDriver Enterprise provides the complete solution - from initial setup through ongoing maintenance and support.
 
+For more details, see [Contract Details](#contract-details).
+
 ---
 
 ## Implementation Process
 
 1. **Initial Consultation**: Discuss your specific testing challenges, application architecture, and infrastructure requirements.
-2. **Expert Test Development**: Our team develops 4 custom tests designed specifically for your application's critical user flows and business logic.
-3. **Integration & Deployment**: Implement tests within your CI/CD pipeline with custom monitoring and reporting configurations.
-4. **Team Training & Ongoing Support**: Comprehensive training for your team plus ongoing technical support and consultation.
+2. **Custom Infrastructure Design**: Configure specialized testing environments tailored to your technology stack and workflow requirements.
+3. **Expert Test Development**: Our team develops 4 custom tests designed specifically for your application's critical user flows and business logic.
+4. **Integration & Deployment**: Implement tests within your CI/CD pipeline with custom monitoring and reporting configurations.
+5. **Team Training & Ongoing Support**: Comprehensive training for your team plus ongoing technical support and consultation.
 
 Complex applications - particularly desktop software, browser extensions, and multi-platform workflows - present unique testing challenges that require specialized infrastructure and deep technical expertise. TestDriver Enterprise addresses these challenges with custom solutions designed specifically for your application and development process.
 
@@ -83,6 +86,7 @@ Complex applications - particularly desktop software, browser extensions, and mu
 
 | Service                           | Timeline      | Description                                                                                      |
 | --------------------------------- | ------------- | ------------------------------------------------------------------------------------------------ |
+| **Infrastructure Design**         | First 7 Days  | Analysis and configuration of specialized testing environments for your application stack.       |
 | **Requirements Analysis**         | First 7 Days  | Comprehensive review of testing requirements and technical specifications.                       |
 | **Custom Test Development**       | First 4 Weeks | Expert creation of 4 fully customized tests (4x4 Guarantee) tailored to your critical workflows. |
 | **Training & Knowledge Transfer** | First 30 Days | Technical training for your team and establishment of ongoing support processes.                 |
@@ -99,7 +103,7 @@ Complex applications - particularly desktop software, browser extensions, and mu
 - **Service Level**: Dedicated support team and technical consultation included.
 - **Usage Tracking**: Monthly runner minute allocation with standard overage rates.
 - **Custom Infrastructure**: Specialized testing environments included for complex applications.
-- **Enterprise Options**: [Self hosting](/getting-started/self-hosting) configurations available.
+- **Enterprise Options**: On-premises and BYOC (Bring Your Own Cloud) configurations available.
 
 ---
 

package/docs/account/pricing.mdx

@@ -19,12 +19,12 @@ TestDriver offers a range of pricing plans to suit different needs, from individ
   </Card>
   <Card title="Enterprise" icon="shield">
     Need advanced features? Contact us for tailored solutions. Starting at
-    $2,000/month.
+    $995/month.
   </Card>
 </CardGroup>
 
 <Tip>
-  Every plan comes with access to the Playwright SDK to get you off the starting
+  Every plan starts with $100 in TestDriver credits to get you off the starting
   line!
 </Tip>
 

package/docs/account/projects.mdx

@@ -23,11 +23,6 @@ From the Project view, you can see all the replays (Dashes) stored for that proj
 
 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.
 
-<Info>
-  The project ID can be used in conjunction with your `lifecycle/postrun.yaml`
-  script to automatically assign a replay to a project. For more info see the
-  (Dashcam section)[/guide/dashcam].
-</Info>
 <Frame caption="Click a Project to view its replays">
   <img src="/images/content/account/newprojectsettings.png" />
 </Frame>

package/docs/cli/overview.mdx

@@ -15,11 +15,11 @@ npx testdriverai@latest <command> [options]
 
 ## Available commands
 
-|         Command          | Description                                                  |
-| :----------------------: | :----------------------------------------------------------- |
-|  [`run`](/commands/run)  | Executes a TestDriver test.                                  |
-| [`edit`](/commands/edit) | Launch interactive mode.                                     |
-| [`help`](/commands/help) | Displays help information for the CLI or a specific command. |
+|        Command         | Description                                                  |
+| :--------------------: | :----------------------------------------------------------- |
+| [`run`](/commands/run) | Executes a TestDriver test.                                  |
+| [`edit`](/commands/edit)         | Launch interactive mode.                                     |
+| [`help`](/commands/help)         | Displays help information for the CLI or a specific command. |
 
 ## Available Flags
 
@@ -27,9 +27,9 @@ npx testdriverai@latest <command> [options]
 | :------------------ | :----------------------------------------------------------------------------------------- |
 | `--heal`            | Launch exploratory mode and attemp to recover if an error or failing state is encountered. |
 | `--write`           | Ovewrite test file with new commands resulting from agentic testing                        |
+| `--headless`        | Run test without opening a browser window (useful for CI/CD environments)                  |
 | `--new`             | Create a new sandbox environment for the test run.                                         |
 | `--summary=<value>` | Output file where AI summary should be saved.                                              |
-| `--junit=<value>`   | Output file where junit report should be saved.                                            |
 
 ## Example usage
 

package/docs/commands/assert.mdx

@@ -22,7 +22,6 @@ The `assert` command validates that a specific condition is true. It ensures tha
 | -------- | --------- | ------------------------------------------------------------------------------------------------------------------ |
 | `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`. |
-| `invert` | `boolean` | (Optional) If set to `true`, will fail if the assertion passes.                                                    |
 
 ## Example usage
 

package/docs/commands/hover-text.mdx

@@ -24,7 +24,6 @@ The `hover-text` command is used to locate text on the screen based on a descrip
 | `description` | `string` | A description of the text and what it represents. The actual text itself shouldn't be included here.                                                                                                                        |
 |   `action`    | `string` | The action to take when the text is found. Available actions are: `click`, `right-click`, `double-click`, `hover`. Also supports `drag-start` and `drag-end` for [dragging text](/commands/hover-image#drag-functionality). |
 |   `method`    |  `enum`  | The matching algorithm to use. Possible values are `turbo` (default) and `ai`.                                                                                                                                              |
-|   `timeout`   | `number` | **(Optional)** The duration in milliseconds to wait for the text to appear. Default is `5000` (5 seconds).                                                                                                                  |
 
 ## Example usage
 
@@ -33,12 +32,11 @@ command: hover-text
 text: Sign Up
 description: link in the header
 action: click
-timeout: 10000 # 10 seconds
 ```
 
 ## Gotchas
 
-- If the text can't be located, it will internally call the [wait-for-text](/commands/wait-for-text) command and wait for the text to appear. The wait `timeout` is 5 seconds by default, and the command fails if the text is not found.
+- If the text can't be located, the command will fail. Ensure the text is visible on the screen and matches exactly.
 - Variations in font size, style, or screen resolution may affect detection accuracy.
 
 ## Notes

package/docs/commands/match-image.mdx

@@ -18,11 +18,10 @@ The `match-image` command is used to locate an image on the screen by matching i
 
 ## Arguments
 
-| Argument | Type      | Description                                                                                                                                                                                                                   |
-| -------- | --------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `path`   | `string`  | The path to the image that needs to be matched. The path needs to be relative to the current test file                                                                                                                        |
-| `action` | `string`  | The action to take when the image is found. Available actions are: `click`, `right-click`, `double-click`, `hover`. Also supports `drag-start` and `drag-end` for [dragging images](/commands/hover-image#drag-functionality) |
-| `invert` | `boolean` | (Optional) If set to `true`, the command will pass when the specified image is NOT detected. Default is `false`.                                                                                                              |
+| Argument | Type     | Description                                                                                                                                                                                                                   |
+| -------- | -------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `path`   | `string` | The path to the image that needs to be matched. The path needs to be relative to the current test file                                                                                                                        |
+| `action` | `string` | The action to take when the image is found. Available actions are: `click`, `right-click`, `double-click`, `hover`. Also supports `drag-start` and `drag-end` for [dragging images](/commands/hover-image#drag-functionality) |
 
 ## Example usage
 

package/docs/commands/press-keys.mdx

@@ -28,7 +28,8 @@ The keys supported are the standard [Windows keys](https://learn.microsoft.com/e
 
 <Tabs>
   <Tab title="Modifiers">
-    - `ctrl`, `shift`, `alt`, `command`, `option`, `win` - Left/right variants:
+    - `ctrl`, `shift`, `alt`, `command`, `option`, `win` 
+    - Left/right variants:
     `ctrlleft`, `ctrlright`, `shiftleft`, `shiftright`, `altleft`, `altright`,
     `optionleft`, `optionright`, `winleft`, `winright`
   </Tab>
@@ -36,7 +37,9 @@ The keys supported are the standard [Windows keys](https://learn.microsoft.com/e
     - All ASCII printable characters: letters `a`–`z`, digits `0`–`9`, common
     punctuation, and `space`.
   </Tab>
-  <Tab title="Function keys">- `f1`–`f24`</Tab>
+  <Tab title="Function keys">
+  - `f1`–`f24`
+  </Tab>
   <Tab title="Navigation">
     - `up`, `down`, `left`, `right`, `home`, `end`, `pageup`, `pagedown`,
     `pgup`, `pgdn`
@@ -54,10 +57,9 @@ The keys supported are the standard [Windows keys](https://learn.microsoft.com/e
     `separator`
   </Tab>
   <Tab title="Media & Browser">
-    - `playpause`, `stop`, `nexttrack`, `prevtrack`, `volumedown`, `volumeup`,
-    `volumemute` - `browserback`, `browserforward`, `browserrefresh`,
-    `browsersearch`, `browserstop`, `browserfavorites`, `browserhome` -
-    `launchapp1`, `launchapp2`, `launchmail`, `launchmediaselect`
+    - `playpause`, `stop`, `nexttrack`, `prevtrack`, `volumedown`, `volumeup`, `volumemute` 
+    - `browserback`, `browserforward`, `browserrefresh`, `browsersearch`, `browserstop`, `browserfavorites`, `browserhome` 
+    - `launchapp1`, `launchapp2`, `launchmail`, `launchmediaselect`
   </Tab>
   <Tab title="IME / International">
     - `hangul`, `hanguel`, `hanja`, `junja`, `kana`, `kanji`, `modechange`,

package/docs/commands/scroll-until-image.mdx

@@ -18,14 +18,13 @@ The `scroll-until-image` command is used to scroll the screen in a specified dir
 
 ## Arguments
 
-|   Argument    |   Type    | Description                                                                                                             |
-| :-----------: | :-------: | :---------------------------------------------------------------------------------------------------------------------- |
-| `description` | `string`  | A description of the image and what it represents.                                                                      |
-|  `direction`  | `string`  | (Optional) The direction to scroll. Available directions are: `up`, `down`, `left`, `right`. Defaults to `down`.        |
-|  `distance`   | `number`  | (Optional) The maximum number of pixels to scroll before giving up. Default is `10000`.                                 |
-|   `method`    | `string`  | (Optional) The method to use to scroll the page. Available methods are: `mouse` and `keyboard`. Defaults to `keyboard`. |
-|    `path`     | `string`  | (Optional) The relative path to the image file that needs to be matched on the screen.                                  |
-|   `invert`    | `boolean` | (Optional) If set to `true`, the command will scroll until the specified image is NOT detected. Default is `false`.     |
+|   Argument    |   Type   | Description                                                                                                             |
+| :-----------: | :------: | :---------------------------------------------------------------------------------------------------------------------- |
+| `description` | `string` | A description of the image and what it represents.                                                                      |
+|  `direction`  | `string` | (Optional) The direction to scroll. Available directions are: `up`, `down`, `left`, `right`. Defaults to `down`.        |
+|  `distance`   | `number` | (Optional) The maximum number of pixels to scroll before giving up. Default is `10000`.                                 |
+|   `method`    | `string` | (Optional) The method to use to scroll the page. Available methods are: `mouse` and `keyboard`. Defaults to `keyboard`. |
+|    `path`     | `string` | (Optional) The relative path to the image file that needs to be matched on the screen.                                  |
 
 <Note>
   Use either the `description` or `path` argument to match an image on the

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

@@ -18,13 +18,12 @@ The `scroll-until-text` command is used to scroll the screen in a specified dire
 
 ## Arguments
 
-|  Argument   |   Type    | Description                                                                                                             |
-| :---------: | :-------: | :---------------------------------------------------------------------------------------------------------------------- |
-|   `text`    | `string`  | The text to find on the screen. Longer and unique are better. Note this is **case sensitive**                           |
-| `direction` | `string`  | (Optional) The direction to scroll. Available directions are: `up`, `down`, `left`, `right`. Defaults to `down`.        |
-|  `method`   | `string`  | (Optional) The method to use to scroll the page. Available methods are: `mouse` and `keyboard`. Defaults to `keyboard`. |
-| `distance`  | `number`  | (Optional) The maximum number of pixels to scroll before giving up. Default is `10000`.                                 |
-|  `invert`   | `boolean` | (Optional) If set to `true`, the command will scroll until the specified text is NOT detected. Default is `false`.      |
+|  Argument   |   Type   | Description                                                                                                             |
+| :---------: | :------: | :---------------------------------------------------------------------------------------------------------------------- |
+|   `text`    | `string` | The text to find on the screen. Longer and unique are better. Note this is **case sensitive**                           |
+| `direction` | `string` | (Optional) The direction to scroll. Available directions are: `up`, `down`, `left`, `right`. Defaults to `down`.        |
+|  `method`   | `string` | (Optional) The method to use to scroll the page. Available methods are: `mouse` and `keyboard`. Defaults to `keyboard`. |
+| `distance`  | `number` | (Optional) The maximum number of pixels to scroll before giving up. Default is `10000`.                                 |
 
 <Note>
 If the method is `keyboard` it just searches for the string by doing `ctrl + f`. 

package/docs/commands/wait-for-image.mdx

@@ -18,11 +18,10 @@ The `wait-for-image` command waits until the specified image is detected on the
 
 ## Arguments
 
-|   Argument    |   Type    | Description                                                                                                       |
-| :-----------: | :-------: | :---------------------------------------------------------------------------------------------------------------- |
-| `description` | `string`  | A description of the image.                                                                                       |
-|   `timeout`   | `number`  | (Optional) The duration in milliseconds to wait for the image to appear. Default is `10000` (10 seconds).         |
-|   `invert`    | `boolean` | (Optional) If set to `true`, the command will wait until the specified image is NOT detected. Default is `false`. |
+|   Argument    |   Type   | Description                                                                                               |
+| :-----------: | :------: | :-------------------------------------------------------------------------------------------------------- |
+| `description` | `string` | A description of the image.                                                                               |
+|   `timeout`   | `number` | (Optional) The duration in milliseconds to wait for the image to appear. Default is `10000` (10 seconds). |
 
 ## Example usage
 

package/docs/commands/wait-for-text.mdx

@@ -18,12 +18,11 @@ The `wait-for-text` command waits until the specified text is detected on the sc
 
 ## Arguments
 
-| Argument  |   Type    | Description                                                                                                      |
-| :-------: | :-------: | :--------------------------------------------------------------------------------------------------------------- |
-|  `text`   | `string`  | The text to find on the screen.                                                                                  |
-| `timeout` | `number`  | (Optional) The duration in milliseconds to wait for the text to appear. Default is `5000` (5 seconds).           |
-| `method`  |  `enum`   | (Optional) The matching algorithm to use. Possible values are `ai` and `turbo`. Default is `turbo`               |
-| `invert`  | `boolean` | (Optional) If set to `true`, the command will wait until the specified text is NOT detected. Default is `false`. |
+| Argument  |   Type   | Description                                                                                            |
+| :-------: | :------: | :----------------------------------------------------------------------------------------------------- |
+|  `text`   | `string` | The text to find on the screen.                                                                        |
+| `timeout` | `number` | (Optional) The duration in milliseconds to wait for the text to appear. Default is `5000` (5 seconds). |
+| `method`  |  `enum`  | (Optional) The matching algorithm to use. Possible values are `ai` and `turbo`. Default is `turbo`     |
 
 ## Example usage
 

package/docs/docs.json

@@ -38,6 +38,7 @@
             "group": "CLI",
             "icon": "terminal",
             "pages": [
+              "/getting-started/cli",
               "/cli/overview",
               {
                 "group": "Commands",
@@ -49,10 +50,7 @@
                 ]
               }
             ]
-          },
-          "/getting-started/self-hosting",
-          "/getting-started/playwright",
-          "/getting-started/vscode"
+          }
         ]
       },
       {
@@ -65,8 +63,7 @@
               "apps/static-websites",
               "apps/desktop-apps",
               "apps/chrome-extensions",
-              "apps/mobile-apps",
-              "apps/tauri-apps"
+              "apps/mobile-apps"
             ]
           },
           {
@@ -103,7 +100,6 @@
               "/guide/authentication",
               "/guide/variables",
               "/guide/lifecycle",
-              "/guide/dashcam",
               "/guide/environment-variables",
               "/action/ami"
             ]
@@ -157,32 +153,39 @@
       {
         "group": "Reference",
         "pages": [
-          {
-            "group": "YAML",
-            "icon": "file-code",
-            "pages": [
-              "/commands/assert",
-              "/commands/exec",
-              "/commands/focus-application",
-              "/commands/hover-image",
-              "/commands/hover-text",
-              "/commands/if",
-              "/commands/match-image",
-              "/commands/press-keys",
-              "/commands/remember",
-              "/commands/run",
-              "/commands/scroll",
-              "/commands/scroll-until-image",
-              "/commands/scroll-until-text",
-              "/commands/type",
-              "/commands/wait",
-              "/commands/wait-for-image",
-              "/commands/wait-for-text"
-            ]
-          }
+          "/commands/assert",
+          "/commands/exec",
+          "/commands/focus-application",
+          "/commands/hover-image",
+          "/commands/hover-text",
+          "/commands/if",
+          "/commands/match-image",
+          "/commands/press-keys",
+          "/commands/remember",
+          "/commands/run",
+          "/commands/scroll",
+          "/commands/scroll-until-image",
+          "/commands/scroll-until-text",
+          "/commands/type",
+          "/commands/wait",
+          "/commands/wait-for-image",
+          "/commands/wait-for-text"
         ]
       }
-    ]
+    ],
+    "global": {
+      "anchors": [
+        {
+          "anchor": "Book a Demo",
+          "href": "https://testdriver.ai/demo",
+          "icon": "calendar"
+        }
+      ]
+    }
+  },
+  "modeToggle": {
+    "enabled": false,
+    "default": "dark"
   },
   "logo": {
     "light": "/images/template/light.png",
@@ -195,18 +198,13 @@
         "label": "Discord",
         "icon": "discord",
         "href": "https://discord.com/invite/cWDFW8DzPm"
-      },
-      {
-        "label": "Book a Demo",
-        "href": "https://form.typeform.com/to/UECf9rDx?typeform-source=docs.testdriver.ai",
-        "icon": "calendar"
-      },
-      {
-        "icon": "gauge-high",
-        "label": "Dashboard",
-        "href": "https://app.testdriver.ai"
       }
-    ]
+    ],
+    "primary": {
+      "type": "button",
+      "label": "Dashboard",
+      "href": "https://app.testdriver.ai"
+    }
   },
   "footer": {
     "socials": {

package/docs/getting-started/vscode.mdx

@@ -1,86 +1,75 @@
 ---
 title: "Install the TestDriver VS Code Extension"
-sidebarTitle: "VS Code"
+sidebarTitle: "VS Code Setup"
 description: "Comprehensive guide to installing and setting up TestDriver for VS Code"
 icon: "file-code"
-tag: BETA
 ---
 
-<iframe
-  className="w-full aspect-video rounded-xl"
-  src="https://www.youtube.com/embed/dell_2tI6nc"
-  title="YouTube video player"
-  frameBorder="0"
-  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
-  allowFullScreen
-></iframe>
-
-The TestDriver VS Code extension is a powerful tool that integrates TestDriver's AI-driven test generation capabilities directly into your development environment:
-
-- Get started with example scripts for different platforms
-- Get syntax highlighting and autocompletion for [TestDriver YAML](/getting-started/editing)
-- Chat with the TestDriver agent to generate tests based on your requirements
-- Save and manage your tests directly within your project
-- Run and debug tests directly from the IDE
-- View test results and logs within the IDE
-
-<Tip>
-  The TestDriver VS Code Extension is currently in beta. If you encounter any
-  issues or have feedback, please let us know [in
-  Discord](https://discord.com/invite/cWDFW8DzPm)
-</Tip>
+<Card
+  title="Get the VS Code Extension"
+  icon="link"
+  href="https://marketplace.visualstudio.com/items?itemName=testdriver.testdriver"
+>
+  Turn your IDE into a powerful computer-use automation tool with our VS Code
+  extension.
+</Card>
 
 <Steps>
-  <Step title="Install the VS Code Extension">
-    
-    Click the button below to install the TestDriver extension for your preferred IDE. Then, follow the setup guide and chat with TestDriver to create your first test.
-
-    <Card
-      horizontal
-      title="VS Code"
-      arrow
-      href="vscode:extension/testdriver.testdriver"
-      icon="/images/content/extension/vscode.svg"
-    ></Card>
-
-    <Card
-      horizontal
-      title="Cursor"
-      arrow
-    href="cursor:extension/testdriver.testdriver"
-    icon="/images/content/extension/cursor.svg"
-
-    > </Card>
-
-    <Card
-      horizontal
-      title="Windsurf"
-      arrow
-      href="windsurf:extension/testdriver.testdriver"
-      icon="/images/content/extension/windsurf.svg"
-    ></Card>
+  <Step title="Initialize Your Project" stepNumber={1}>
+    Set up your project with:
+
+    ```bash
+    npx testdriverai@latest init
+    ```
+
+    This creates a `.env` file and sample workflow files.
 
   </Step>
-  <Step title="Set Your TestDriver API Key">
-    
-    After installing the extension, you'll need to set your TestDriver API key in the extension settings.
+  <Step title="Run TestDriver in Interactive Mode" stepNumber={2}>
+    Start TestDriver in interactive mode to create and refine tests dynamically:
 
-    1. Open the command palette (Cmd+Shift+P or Ctrl+Shift+P).
-    2. Search for "Preferences: Open Settings (UI)" and select it.
-    3. In the search bar, type "TestDriver" to filter the settings.
-    4. Find the "TestDriver: Set API Key" field and enter your API key from [the TestDriver dashboard](https://app.testdriver.ai/team).
+    ```bash
+    npx testdriverai@latest
+    ```
 
-    <Tip>You can also set the `TD_API_KEY` environment variable in your system if you prefer not to enter it directly in the extension settings.</Tip>
+    Once started, you can use commands like `/explore`, `/run`, and `/save` to interactively build and test your flows.
 
   </Step>
-  <Step title="Choose a Platform">
-    Click on the TestDriver icon in the sidebar to open the extension panel and choose a platform to get started (Web, Desktop, or Mobile).
+  <Step title="Define Your Test Steps" stepNumber={3}>
+    Use natural language to describe what you want to test. For example:
+
+    ```
+    > Open Google Chrome and search for "testdriverai"
+    ```
+
+    TestDriver will generate steps like:
+
+    ```yaml
+    - command: focus-application
+      name: Google Chrome
+    - command: hover-text
+      text: Search Google or type a URL
+      description: main search bar
+      action: click
+    - command: type
+      text: testdriverai
+    - command: press-keys
+      keys:
+        - enter
+    ```
+
   </Step>
-  <Step title="Create Your First Test">
-    Now chat with the TestDriver agent to create your first test! Describe what you want to test, and the agent will generate the test steps for you.
+  <Step title="Refine and Save Your Test" stepNumber={4}>
+    - Save your test with `/save` to generate a reusable YAML file.
+    - Use `/run` to run the test.
   </Step>
-  <Step title="Run your test">
-    Run your test by clicking the "Run" button in the extension panel. You can view the test results and logs directly within VS Code's Test Explorer. [Learn more about running tests in VS Code](https://code.visualstudio.com/docs/debugtest/testing). 
+  <Step title="Run Saved Tests" stepNumber={5}>
+    Once saved, you can run your test file anytime:
+
+    ```bash
+    npx testdriverai@latest run path/to/test.yaml
+    ```
+
   </Step>
 </Steps>
 

package/docs/guide/environment-variables.mdx

@@ -11,13 +11,13 @@ import GitignoreWarning from "/snippets/gitignore-warning.mdx";
 The supported environment variables in TestDriver are:
 
 <div className="env-vars-table">
-  | Variable | Type | Description |
+  |   Variable      |   Type    | Description                                                                     |
   |:---------------:|:---------:|---------------------------------------------------------------------------------|
-  | TD_ANALYTICS | boolean | Send analytics to TestDriver servers. This helps
-  provide feedback to inform our roadmap. | | TD_API_KEY | string | Set this to
-  spawn VMs with TestDriver Pro. |
+  | TD_ANALYTICS    | boolean   | Send analytics to TestDriver servers. This helps provide feedback to inform our roadmap. |
+  | TD_API_KEY      | string    | Set this to spawn VMs with TestDriver Pro.                                        |
 </div>
-<GitignoreWarning />
+  
+<GitignoreWarning/>
 ## Example
 
 ```bash .env