Load Chrome Extensions

Install Chrome extensions into cloud browser sessions so they behave identically to local browsers with your required extensions.

Overview

Your agent workflow depends on a Chrome extension - an ad blocker, a cookie manager, or a custom tool your team built. Without it, the browser behaves differently and your automation may not work as expected.

The Extension Service solves this by letting you register Chrome extensions and inject them into TestMu AI Browser Cloud sessions. You provide a cloud-hosted URL (S3) for each extension, and TestMu AI downloads and installs it into the browser instance when the session starts. Your cloud sessions behave the same way as your local browser.

Before You Begin

Your extension must be hosted at a cloud URL (such as an S3 bucket) before you can register it. See Current Limitations for details on what is supported today.

Loading Extensions into a Session

First, register an extension. Then pass its ID when creating a session:

// Step 1: Register (one time)
const ext = await client.extensions.register({
    name: 'My Extension',
    version: '1.0.0',
    cloudUrl: 'https://s3.amazonaws.com/bucket/extension.zip',
});

// Step 2: Load into sessions
const session = await client.sessions.create({
    adapter: 'puppeteer',
    extensionIds: [ext.id],    // Pass registered extension IDs
    lambdatestOptions: { ... }
});

When extensionIds are provided, the session manager fetches the cloud URLs and adds them to TestMu AI capabilities as lambda:loadExtension.

Managing Extensions

const extensions = await client.extensions.list();

const ext = await client.extensions.get('ext_abc123');

await client.extensions.delete('ext_abc123');

Extension Object

interface Extension {
    id: string;
    name: string;
    version: string;
    description?: string;
    enabled: boolean;
    createdAt: string;
    cloudUrl?: string;     // S3 URL
    localPath?: string;    // Local file path
}

Supported Formats

• .zip archives containing Chrome extension files
• .crx Chrome extension packages

Current Limitations

• Extension upload to S3 must be done manually (via curl, AWS CLI, or your upload pipeline)
• The automated upload API through TestMu AI is not yet integrated
• Extensions only work with cloud sessions