k6-browser support in stagehand

[inancgumus]

Our users want to use Grafana's k6-browser through stagehand.

However, it does't support k6-browser. The k6-browser drives Chromium through CDP. Its API is roughly similar to Playwright. For example, we also have BrowserContext and Page types.

Can we add a support for k6-browser to stagehand?

Are you willing to contribute to implementing this feature or fix?

• Yes, I can submit a PR
• Yes, but I need guidance
• No, I cannot contribute at this time

[miguelg719]

We're strongly focused on direct control of the browser via CDP since our v3 release (having migrated entirely off of playwright). Anything exposing a CDP url is already supported on Stagehand!

[inancgumus]

@miguelg719, I'm not sure what you mean by exposing a CDP URL. We're like Playwright:

We drive Chromium using CDP.

Considering this Playwright example from your documentation:

// Navigate using Playwright
await pwPage.goto("https://example.com");

// Use Stagehand's AI methods with the Playwright page
await stagehand.act("click the login button", { page: pwPage });

Here, that pwPage is a Playwright Page type. Looking at your code, the page field only accepts certain types; one of them is this Playwright Page type. However, k6-browser has its own Page type.

I'm wondering if our users can pass a k6-browser Page object to stagehand? So, they can write k6-browser scripts with stagehand and allow stagehand to drive our API.