@testdriverai/agent 7.8.0-canary.10

package/docs/snippets/tests/wait-for-image-yaml.mdx

@@ -0,0 +1,18 @@
+```yaml highlight={14-17}
+version: 6.0.0
+steps:
+  - prompt: go to testdriver.ai and wait for the hero image to load
+    commands:
+      - command: press-keys
+        keys:
+          - ctrl
+          - l
+      - command: type
+        text: testdriver.ai
+      - command: press-keys
+        keys:
+          - enter
+      - command: wait-for-image
+        description: the hero section image
+        timeout: 10000 # 10 seconds
+```

package/docs/snippets/tests/wait-for-text-replay.mdx

@@ -0,0 +1,7 @@
+<div className="replay-block">
+  <iframe
+    src="https://app.testdriver.ai/replay/68a594f73f4291f46c418d42?share=TMvd5NhizKhNsWnnuyl5A&embed=true&timestamp=90000&playbackRate=5"
+    width="1000"
+    height="350"
+  />
+</div>

package/docs/snippets/tests/wait-for-text-yaml.mdx

@@ -0,0 +1,18 @@
+```yaml highlight={14-17}
+version: 6.0.0
+steps:
+  - prompt: go to testdriver.ai and verify the page loads
+    commands:
+      - command: press-keys
+        keys:
+          - ctrl
+          - l
+      - command: type
+        text: testdriver.ai
+      - command: press-keys
+        keys:
+          - enter
+      - command: wait-for-text
+        text: Book a Demo
+        timeout: 10000 # 10 seconds
+```

package/docs/snippets/tests/wait-replay.mdx

@@ -0,0 +1,7 @@
+<div className="replay-block">
+  <iframe
+    src="https://app.testdriver.ai/replay/68a592bd3f4291f46c418d40?share=OxDLtTuEFduInsKp8Nlqfg&embed=true&timestamp=90000&playbackRate=5"
+    width="1000"
+    height="350"
+  />
+</div>

package/docs/snippets/tests/wait-yaml.mdx

@@ -0,0 +1,13 @@
+```yaml highlight={5, 6}
+version: 6.0.0
+steps:
+  - prompt: wait for 5 seconds and type testdriver
+    commands:
+      - command: wait
+        timeout: 5000 # 5 seconds
+      - command: type
+        text: testdriver
+      - command: press-keys
+        keys:
+          - enter
+```

package/docs/styles.css

@@ -0,0 +1,65 @@
+.comparison-table th {
+  font-size: 18px;
+  padding: 12px 30px;
+}
+
+.comparison-table td {
+  padding: 12px 30px;
+  font-size: 16px;
+  line-height: 1.2;
+  text-align: start;
+}
+
+.comparison-table code {
+  font-size: 1em;
+}
+
+.env-vars-table table {
+  width: 120%;
+}
+
+.env-vars-table th {
+  font-size: 18px;
+  padding: 12px 30px;
+  border: 1.5px solid #05f1d9;
+}
+
+.env-vars-table td {
+  padding: 12px 30px;
+  font-size: 16px;
+  line-height: 1.5;
+  border: 1.5px solid #05f1d9;
+  vertical-align: middle;
+}
+
+.env-vars-table code {
+  font-size: 0.9em;
+}
+
+.prose
+  :where(a code):not(:where([class~="not-prose"], [class~="not-prose"] *)) {
+  border-bottom: none !important;
+  padding-bottom: 0 !important;
+  text-decoration: none !important;
+}
+
+.card img {
+  background-color: transparent !important;
+}
+
+.replay-block {
+  width: 100vw;
+  margin-left: 50%;
+  transform: translateX(-50%);
+  justify-content: center;
+  display: flex;
+}
+
+img[src$=".svg"] {
+  background: transparent !important;
+}
+
+img[src$="https://tauri.app/favicon.svg"]
+{
+  opacity: 0.3;
+}

package/docs/v6/account/dashboard.mdx

@@ -0,0 +1,16 @@
+---
+title: "Dashboard"
+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.

package/docs/v6/account/enterprise.mdx

@@ -0,0 +1,110 @@
+---
+title: "Enterprise"
+sidebarTitle: "For Enterprise"
+description: "The TestDriver 4x4 Guarantee!"
+icon: gem
+---
+
+import { calendar } from "/snippets/calendar-link.mdx";
+
+TestDriver Enterprise is designed for fast-moving teams that need comprehensive QA coverage for complex applications. Our **4x4 Guarantee** ensures you get 4 custom tests created specifically for your application within your first 4 weeks.
+
+We specialize in testing scenarios that other tools can't handle - desktop applications, browser extensions, multi-platform workflows, and complex integrations that require custom infrastructure and expert support.
+
+<Card
+  title="Schedule a Consultation"
+  icon="calendar"
+  href="https://calendly.com/d/cq23-qyn-3v6/testdriver-ai-demo"
+  link
+>
+  Discuss your testing requirements and custom infrastructure needs.
+</Card>
+
+---
+
+## Enterprise Plans
+
+TestDriver Enterprise plans start at **$2,000/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.
+- Full CI/CD pipeline integration with custom configurations.
+- Dedicated infrastructure and ongoing support for complex testing scenarios.
+
+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.
+
+<CardGroup cols={3}>
+  <Card title="Custom Desktop & Extension Testing">
+    Test complex desktop applications and browser extensions that other tools
+    can't handle.
+  </Card>
+  <Card title="Multi-App Workflow Testing">
+    Test sophisticated workflows that span multiple applications and platforms.
+  </Card>
+  <Card title="Enterprise Infrastructure & Support">
+    Get dedicated infrastructure and expert support for your unique testing
+    challenges.
+  </Card>
+</CardGroup>
+
+## Enterprise Features
+
+TestDriver Enterprise provides comprehensive support for fast-moving teams with complex testing requirements:
+
+- **Complex Application Support**: Full testing capabilities for desktop applications, Chrome extensions, mobile apps, and web applications that require specialized infrastructure.
+- **4x4 Custom Test Creation**: Our expert team creates 4 fully customized tests tailored to your specific application and workflows within the first 4 weeks.
+- **Multi-Platform Workflows**: Test complex scenarios spanning multiple applications, browsers, and operating systems.
+- **Unlimited Parallel Testing**: Scale your testing across custom infrastructure without limitations.
+- **Continuous Test Execution**: Automated test runs integrated with your development and deployment cycles.
+- **Intelligent Reporting**: Detailed analytics and quality reports delivered to your team.
+- **Self-Healing Test Maintenance**: AI-powered test maintenance that adapts to application changes.
+- **Custom CI/CD Integration**: Tailored integration with your existing development pipeline.
+- **Enterprise Dashboards**: Advanced analytics and monitoring with custom metrics and insights.
+- **Dedicated Infrastructure**: Specialized testing environments configured for your application stack.
+- **Expert Support**: Ongoing technical support and consultation from our testing specialists.
+
+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.
+
+---
+
+## 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.
+
+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.
+
+---
+
+## Implementation Timeline
+
+| Service                           | Timeline      | Description                                                                                      |
+| --------------------------------- | ------------- | ------------------------------------------------------------------------------------------------ |
+| **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.                 |
+| **Continuous Execution**          | Ongoing       | Automated test execution with specialized monitoring, reporting, and maintenance.                |
+
+---
+
+## Contract Information
+
+- **4x4 Guarantee**: 4 custom tests delivered within your first 4 weeks of service.
+- **Test Ownership**: Complete ownership of all tests - modify, duplicate, or distribute as needed.
+- **Payment Terms**: Monthly or annual billing options available.
+- **Contract Term**: Annual contracts with flexible payment schedules.
+- **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.
+
+---
+
+## Get Started
+
+<a href={calendar}>**Schedule a consultation**</a> to discuss your testing
+requirements and learn how TestDriver Enterprise can support your team's
+development process.

package/docs/v6/account/pricing.mdx

@@ -0,0 +1,33 @@
+---
+title: "Pricing"
+sidebarTitle: "Pricing"
+description: "Explore TestDriver's pricing plans and features."
+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}>
+  <Card title="Hobby" icon="check">
+    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.
+  </Card>
+  <Card title="Enterprise" icon="shield">
+    Need advanced features? Contact us for tailored solutions. Starting at
+    $2,000/month.
+  </Card>
+</CardGroup>
+
+<Tip>
+  Every plan comes with access to the Playwright SDK 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).

package/docs/v6/account/projects.mdx

@@ -0,0 +1,33 @@
+---
+title: "TestDriver Projects"
+sidebarTitle: "Projects"
+description: "Manage your projects and workflows with TestDriver."
+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">
+  <img src="/images/content/account/projectpage.png" />
+</Frame>
+
+From the Project view, you can see all the replays (Dashes) stored for that project. Click one to see it. These will also be linked in CI for any pull requests or branches that have been tested with TestDriver.
+
+<Frame caption="Click a Replay to view, comment or share ">
+  <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.
+
+<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/v6/account/team.mdx

@@ -0,0 +1,35 @@
+---
+title: "Team"
+sidebarTitle: "Team"
+description: "Manage your team and collaborate with TestDriver."
+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>
+
+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>
+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.

package/docs/v6/action/ami.mdx

@@ -0,0 +1,109 @@
+---
+title: "Customizing the VM Image"
+sidebarTitle: "Custom VM Image"
+description: "How customize the TestDriver VM Image for robust test execution."
+icon: "image"
+---
+
+<Tip>
+  This guide is specifically for [Enterprise Plan
+  customers](/account/enterprise) who have access to the shared TestDriver AMI.
+  If you are on a different plan, please contact your account manager for more
+  information.
+</Tip>
+
+<Steps>
+  <Step title="Send Us Your AWS Account ID">
+    To begin, send your **12-digit AWS account ID** to your **TestDriver account manager**. We'll share the AMI directly with your AWS account using [Amazon's explicit AMI sharing process](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/sharingamis-explicit.html).
+  </Step>
+  <Step title="Wait for Confirmation">
+    Your account manager will notify you when the AMI has been shared with your
+    account. You will receive the **AMI ID** (e.g., `ami-0abcd1234efgh5678`) and your **RDP Username \+ Password**.
+  </Step>
+  <Step title="Launch and Connect with RDP">
+    Once you have the AMI ID & RDP credentials from the previous step, launch an EC2 instance and connect via RDP:
+
+    1. Ensure your **security group allows RDP (TCP port 3389)**.
+    2. In the EC2 Console, select your instance → **Connect \> RDP Client**.
+    3. Download the `.rdp` file and launch it with the [Windows App](https://adoption.microsoft.com/en-us/windows-app/)\
+       Alternatively, copy the public IP and paste it into your RDP client.
+    4. Login using your **RDP Username \+ Password** (e.g. `testdriver` \+ `•••••••••`) provided by your account manager.
+
+    <Note>
+      You will access a full Windows desktop where TestDriver is pre-installed and ready for customization.
+    </Note>
+
+  </Step>
+
+  <Step title="Change the Windows password">
+    Inside the Windows desktop environment:
+
+    1. Open up Powershell
+    2. Run `C:\testdriver\RotateLocalPasswords.ps1`
+    3. Copy the password presented in the output to a safe place. This is the only chance to copy the password.
+    4. Restart the instance and double check you can log in before continuing.
+
+    Note that this will change the password for the testdriver and rdp_local accounts, but Administrator will remain as a password you can only retreive through the AWS EC2 UI ((Instructions Here)[https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/connect-rdp.html#retrieve-initial-admin-password]).
+
+  </Step>
+
+  <Step title="Customize the Instance">
+    Inside the Windows desktop environment:
+
+    1. **Download and install your application** using a browser, Git, PowerShell, or other tools.
+    2. Add any required system configuration, environment variables, or startup scripts.
+    3. Verify the full setup works correctly in the sandbox.
+
+    Common use cases:
+    - Pull from GitHub or your artifact store
+    - Configure your app with test credentials or environment variables
+    - Enable logging or install monitoring tools
+
+  </Step>
+
+  <Step title="Create Your Custom AMI">
+    Once your customizations are complete, create an AMI from your instance:
+
+    1. In the EC2 Console, select your customized instance.
+    2. Go to **Actions** → **Image and templates** → **Create image**.
+    3. Provide a descriptive **Image name** and **Description**.
+    4. Click **Create image** to start the AMI creation process.
+    5. Wait for the AMI status to change from "pending" to "available".
+
+    <Note>The AMI creation process may take several minutes depending on the instance size and customizations.</Note>
+
+  </Step>
+
+  <Step title="Share Your AMI and Use with TestDriver CLI">
+    After creating your custom AMI:
+
+    1. **Share the AMI ID** with your **TestDriver account manager** so we can launch it in our infrastructure. Follow [Amazon's explicit AMI sharing process](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/sharingamis-explicit.html) if needed.
+    2. Once confirmed, you can reference the AMI directly from your machine using the TestDriver CLI:
+
+    ```bash
+    testdriverai --sandbox-ami=ami-0abcd1234efgh5678
+    ```
+
+    This instructs the CLI to launch a sandbox using **your customized AMI**, enabling test execution in your environment.
+
+  </Step>
+</Steps>
+
+---
+
+## 🔐 Best Practices & Security
+
+- Always use **strong RDP passwords** and keep your key pairs secure.
+- Apply **Windows Updates** to stay current with patches.
+- Use **IAM roles with least privilege** to access other AWS resources.
+- Consider **encrypting your volumes and AMI** if handling sensitive data.
+
+---
+
+### 🤝 Need Help?
+
+Your TestDriver account manager is available to support you with:
+
+- AMI access and customization
+- CLI configuration
+- Troubleshooting sandbox execution

package/docs/v6/action/performance.mdx

@@ -0,0 +1,105 @@
+---
+title: "Optimizing Performance in TestDriver"
+sidebarTitle: "Performance Optimization"
+description: "Optimizing Performance in TestDriver"
+icon: "rabbit-running"
+---
+
+## Overview
+
+Optimizing your TestDriver tests can significantly reduce execution time, ensuring faster feedback for developers and smoother CI/CD workflows. While TestDriver's AI-powered capabilities are robust, using them efficiently is key to achieving the best performance.
+
+---
+
+## Tips for improving performance
+
+### 1. Use parallel testing
+
+Parallel testing allows you to split your test actions into multiple files and run them simultaneously. This can drastically reduce the total runtime of your test suite.
+
+#### How to implement parallel testing
+
+- Divide your test steps into smaller, independent YAML files.
+- Use a test matrix strategy to execute these files in parallel.
+
+<Warning>
+  The [`run`](/commands/run) command is used in your test files to run other
+  test files. This is useful for breaking down large tests into smaller, more
+  manageable pieces. To run multiple separate tests, use a test matrix strategy.
+</Warning>
+
+#### Example
+
+```yaml .github/workflows/testdriver.yaml focus={3-9, 14}
+run tests:
+  name: Run tests in parallel
+  strategy:
+    matrix:
+      test_file:
+        - tests/login.yaml
+        - tests/search.yaml
+        - tests/cart.yaml
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Run the tests
+          run: npx testdriverai@latest run testdriver/${{ matrix.test_file }}
+          env:
+            FORCE_COLOR: 3
+            TD_API_KEY: ${{ secrets.TD_API_KEY }}
+            TD_WEBSITE: https://testdriver-sandbox.vercel.app
+            TD_THIS_FILE: ${{ matrix.test }}
+```
+
+---
+
+### 2. Use optimized matching methods
+
+For actions like [`hover-text`](/commands/hover-text), [`wait-for-text`](/commands/wait-for-text), and [`scroll-until-text`](/commands/scroll-until-text), use the `turbo` matching method instead of `ai`. The `turbo` method uses text similarity to quickly compute the most relevant match, making it about 40% faster than the `ai` method.
+
+#### Example
+
+```yaml
+command: [`hover-text`](/commands/hover-text)
+text: Sign In
+description: login button
+action: click
+method: turbo
+```
+
+<Note>
+  `turbo` is the default method that is currently implemented. The other method
+  being `ai`
+</Note>
+
+---
+
+### 3. Use `async` asserts
+
+The [`assert`](/commands/assert) command supports the `async: true` property, allowing you to create non-blocking assertions. This means your tests can continue running while the assertion is being validated, saving valuable time.
+
+#### Example
+
+```yaml
+command: [`assert`](/commands/assert)
+expect: The user is logged in
+async: true
+```
+
+---
+
+## Best practices
+
+- **Minimize AI Matching**: Use AI-powered matching methods only when necessary. For common actions, rely on optimized methods like `turbo`.
+- **Break Down Tests**: Split large, monolithic test files into smaller, focused tests to enable parallel execution.
+- **Leverage Asynchronous Features**: Use `async` properties wherever possible to avoid blocking test execution.
+- **Monitor Performance**: Regularly review test execution times and identify bottlenecks.
+
+---
+
+## Notes
+
+- Optimizing performance not only saves time but also reduces resource usage, making your CI/CD pipelines more efficient.
+- For large test suites, combining parallel testing with optimized matching methods can lead to significant time savings.
+- Always balance performance optimizations with test reliability to ensure accurate results.

package/docs/v6/action/secrets.mdx

@@ -0,0 +1,93 @@
+---
+title: "Managing Secrets"
+sidebarTitle: "Secrets Management"
+description: "Discover how to securely configure and optimize your TestDriver CLI environment for seamless CI/CD workflows."
+icon: "asterisk"
+---
+
+## Overview
+
+When using TestDriver to test your application, you may need to securely store and use sensitive information such as usernames, passwords, API keys, or other secrets. Every DevOps platform provides a secure way to manage these secrets, ensuring they aren't exposed in your test files or logs.
+
+---
+
+## Why use secrets?
+
+- **Security**: Secrets are encrypted and stored securely in your DevOps platform.
+- **Masking**: TestDriver automatically masks secrets in all test output, including debugging logs.
+- **Reusability**: Secrets can be reused across multiple workflows and test files.
+
+---
+
+## Step 1: Replace hardcoded secrets in test files
+
+To securely use secrets in your TestDriver test files, replace hardcoded values with placeholders in the format `${TD_YOUR_SECRET}`. TestDriver will parse and mask any secrets that begin with `TD_`.
+
+### Example test file
+
+```yaml login.yaml highlight={11, 12, 21, 22}
+version: 6.0.0
+steps:
+  - prompt: sign in with username and password
+    commands:
+      - command: focus-application
+        name: Google Chrome
+      - command: hover-text
+        text: Email or phone
+        description: email input field
+        action: click
+      - command: type
+        text: ${TD_USERNAME}
+      - command: hover-text
+        text: Next
+        description: next button after entering email
+        action: click
+      - command: hover-text
+        text: Password
+        description: password input field
+        action: click
+      - command: type
+        text: ${TD_PASSWORD}
+      - command: hover-text
+        text: Log In
+        description: log in button
+        action: click
+```
+
+---
+
+## Step 2: Add secrets to DevOps platform
+
+In this example we'll use GitHub Actions, but the process is similar for other platforms like GitLab CI/CD, CircleCI, or Jenkins.
+
+1. Navigate to your GitHub repository.
+2. Go to **Settings** > **Secrets and variables** > **Actions**.
+3. Click **New repository secret**.
+4. Add your secrets (for example, `TD_USERNAME`, `TD_PASSWORD`, `TD_API_KEY`).
+
+For detailed instructions, refer to the [GitHub Docs on using secrets](https://docs.github.com/en/actions/security-guides/encrypted-secrets).
+
+---
+
+## Step 3: Supply secrets to TestDriver CLI
+
+When running TestDriver tests via the CLI in GitHub Actions, supply your secrets in the `env` section of the workflow step.
+
+<Card title="Adding secrets to CI" icon="link" href="/guide/authentication">
+  Check out our authentication page to see how to add secrets in your CI
+  workflow.
+</Card>
+
+## Best practices
+
+- **Use Descriptive Names**: Name your secrets clearly (for example, `TD_USERNAME`, `TD_PASSWORD`) to make them easy to identify.
+- **Rotate Secrets Regularly**: Update your secrets periodically to enhance security.
+- **Limit Access**: Only provide access to secrets for workflows and team members that require them.
+
+## <Note>To ensure all secrets are masked in logs, use the `TD_` prefix.</Note>
+
+## Notes
+
+- Secrets are encrypted and only accessible during the workflow run.
+- TestDriver automatically masks secrets in test output to prevent accidental exposure.
+- For additional security, avoid hardcoding sensitive information in your test files or workflows.