Skip to content

fix(integrations): harden live browser tools - #2687

Draft
shrey150 wants to merge 3 commits into
agent/refresh-integrations-readmesfrom
agent/fix-integrations-e2e
Draft

fix(integrations): harden live browser tools#2687
shrey150 wants to merge 3 commits into
agent/refresh-integrations-readmesfrom
agent/fix-integrations-e2e

Conversation

@shrey150

@shrey150 shrey150 commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

Summary

  • omit CrewAI-generated null values before invoking MCP tools so run({ code }) satisfies the codemode schema
  • add allowlisted local Chrome controls for headless mode, executable selection, and sandbox behavior in the TypeScript and Deep Agents runtimes
  • turn unsupported Extensions.loadUnpacked CDP responses into an actionable compatible-Chrome error
  • document the local Chrome requirements and security tradeoff

End-to-end evidence

Using a public https://example.com task and a real Browserbase browser, I exercised run, snapshot, and screenshot through:

  • core MCP
  • CrewAI
  • Deep Agents / LangChain MCP tools
  • Eve native tools
  • Mastra
  • Vercel AI SDK

All six paths navigated successfully, returned the expected title/snapshot, and produced a PNG. The Eve keep-alive session used by the smoke test was explicitly released.

A local-browser smoke test also verified the new settings reach the launcher. The only Chromium available in the test host was Playwright's bundled build, which returns Method not available for Extensions.loadUnpacked; this PR now explains that a compatible Chrome build is required instead of surfacing the raw CDP error.

Verification

  • SDK: build + 187 unit tests
  • integrations core: build, typecheck + 20 tests
  • Eve: typecheck + 5 tests
  • Mastra: typecheck + 2 tests
  • Vercel AI SDK: typecheck + 2 tests
  • CrewAI: Ruff + 4 tests
  • Deep Agents: Ruff + 8 tests

Summary by cubic

Hardens live browser tools across integrations. Adds headless/executable/sandbox controls for local Chrome with env validation, clarifies unsupported extension-loading errors, and drops CrewAI nulls before MCP calls.

  • New Features

    • Local Chrome controls and validation via STAGEHAND_HEADLESS, STAGEHAND_CHROME_PATH, STAGEHAND_CHROMIUM_SANDBOX in TS core and deepagents; local mode can run headless, pick an executable, and toggle the sandbox.
    • Docs: note the local Chrome requirement, Browserbase isolation, and sandbox tradeoffs across crewai, deepagents, eve, mastra, and vercel-ai.
  • Bug Fixes

    • crewai: omit None values before MCP tool calls so run({ code }) matches the schema.
    • sdk-ts: convert "Extensions.loadUnpacked" “method not found/available” responses into a clear “incompatible Chrome build” error.

Written for commit 6793c7d. Summary will update on new commits.

Review in cubic

@changeset-bot

changeset-bot Bot commented Aug 10, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 6793c7d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant