[talge-a11y]

Summary

Adds a browser module to the SDK so backend code can run browser automation on remote browser sessions. It is available only on base44.asServiceRole.

• getSession(options?) creates a session and returns a CDP connection URL to use with Playwright, Puppeteer or Stagehand. It also returns an end() helper.
• endSession(sessionId) ends a session that was created in an earlier request.
• captureDebugArtifacts turns recordings and logs on or off. It defaults to true.
• sessionTimeoutSeconds sets a custom session timeout. The backend clamps it and applies its own default when the option is omitted.

Backend counterpart: base44-dev/apper#31752.

Testing

Unit tests in packages/sdk/tests/unit/browser.test.ts cover request mapping, option forwarding, error codes and the service-role requirement.

[github-actions]

🚀 Package Preview Available!

---

Install this PR's preview build with npm:

npm i @base44-preview/sdk@0.8.55-pr.328.bc88e75

Prefer not to change any import paths? Install using npm alias so your code still imports @base44/sdk:

npm i "@base44/sdk@npm:@base44-preview/sdk@0.8.55-pr.328.bc88e75"

Or add it to your package.json dependencies:

{
  "dependencies": {
    "@base44/sdk": "npm:@base44-preview/sdk@0.8.55-pr.328.bc88e75"
  }
}

• 📦 Preview Package: @base44-preview/sdk@0.8.55-pr.328.bc88e75
• 🔗 View this commit on GitHub

---

_{Preview published to npm registry — try new features instantly!}

[davidsu]

Approved, with a few points:

1. Release order (question). BrowserModule goes into the public docs (types-to-expose.json), but /api/v1/browser-sessions isn't on apper main yet (only on the browser_automation_* branches). If the SDK ships first, getSession() 404s for anyone following the docs. What's the plan: hold the docs exposure until the endpoint is live, or is that fine for a "preliminary" release?

2. Naming: getSession() → createSession()? Every call creates (and bills) a fresh session, and "get" reads as idempotent. Public API names are hard to change after release, so now's the cheap moment. The brain contract test in apper would need the same rename.

3. Timeout docs (browser.types.ts, sessionTimeoutSeconds): the backend clamps to 60–900 s, defaults to 300, and applies it as total session lifetime. Worth stating those here instead of "depending on the provider…", so users don't have to guess.

4. nit, test (browser.test.ts:188): nock.pendingMocks() is always [] here because nothing is mocked, so it can't catch a request. nock.disableNetConnect() in this test, or a mock plus expect(scope.isDone()).toBe(false), would actually prove no request was sent.

5. Docs example (browser.types.ts:80): does browser.contexts()[0] exist when connectionScope is 'page'? If contexts can be empty, browser.contexts()[0]?.pages()[0] ?? await browser.newPage() is safer for people who copy-paste.

I was missing context, researched and found some in #feat-browser-api and #browserbase-base44

agent: review.328

[github-actions]

🚀 Package Preview Available! (@base44/platform)

---

Install this PR's preview build with npm:

npm i @base44-preview/platform@0.5.0-pr.328.bc88e75

Prefer not to change any import paths? Install using npm alias so your code still imports @base44/platform:

npm i "@base44/platform@npm:@base44-preview/platform@0.5.0-pr.328.bc88e75"

Or add it to your package.json dependencies:

{
  "dependencies": {
    "@base44/platform": "npm:@base44-preview/platform@0.5.0-pr.328.bc88e75"
  }
}

• 📦 Preview Package: @base44-preview/platform@0.5.0-pr.328.bc88e75
• 🔗 View this commit on GitHub

---

_{Preview published to npm registry — try new features instantly!}