Add browser session parity options to MCP#110
Draft
IlyaasK wants to merge 3 commits into
Draft
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
manage_browserscreate with SDK 0.58 browser-session options:start_url,chrome_policy,gpu, and telemetry category controlsmanage_browsersupdate for supported session settings:disable_default_proxy, proxy/profile updates, viewport updates, and telemetry updatesValidation
bunx prettier --write src/lib/mcp/tools/browsers.tsgit diff --checkKERNEL_CLI_PROD_CLIENT_ID=dummy-prod KERNEL_CLI_STAGING_CLIENT_ID=dummy-staging KERNEL_CLI_DEV_CLIENT_ID=dummy-dev NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY=pk_test_Y2xlcmsuZXhhbXBsZS5jb20k bun run buildhttp://127.0.0.1:3002/mcpwithAPI_BASE_URL=http://127.0.0.1:3001: initialized MCP, verifiedmanage_browserswas listed, created a short-lived headless browser withstart_url,chrome_policy, telemetry, and viewport options, updated telemetry/viewport through the newupdateaction, retrieved it, and deleted itNotes
disable_default_proxy: truethrough the same localhost MCP path reached the API but the local backend returned500 proxy swap did not complete; browser cleanup succeeded. The MCP request wiring is present, but that backend behavior was not green in local smoke.