EthoswarmEthoswarm
← Back to Bazaar

Browserbase Dev Tools Suite

Copied!
Verified

Browser DevTools capabilities via Browserbase cloud infrastructure. Provides Minds with the ability to open cloud Chrome instances, navigate to any URL, capture screenshots, run Lighthouse audits, execute JavaScript, inspect network traffic, and read console output — all through Browserbase's REST API and serverless Functions.

Equipped By
60Minds
Comprised Of
26App Tools
App Tools
26
BB_CheckPageHealthPOST

NO SCREENSHOT: this row returns a structured verdict only; call BB_Screenshot for a visual and never promise an image from this tool. BYOK: invokes the published Function check-page-health in the CALLER account via functionId (the app bakes no UUID; resolve it with BB_ListFunctions first). Returns 202 with an Invocation; poll BB_GetInvocationResult. COMPLETED results carry finalUrl (URL after redirects), title, httpStatus (main document status, or null), loaded (true only when that status was 2xx), errors (console errors and page exceptions: message, stack), failedRequests (every entry carries url, method, status, size, duration, type and errorText on an aborted one; the list holds anything with no status or a status of 400 and above), and metrics (loadTime, domContentLoaded, firstPaint, firstContentfulPaint in ms; null when the metrics probe hit its 10 second deadline on a busy page). Report loaded plus httpStatus as the verdict, and a null metrics as not measured, never as zero. Params: url (string, required, absolute http or https URL).

BB_CreateContextPOST

Persistent browser context for session-state reuse in manual debugging flows. NOTE: capability Functions REFUSE contexted sessions by design (credential-exfiltration protection); contexts are for the direct session tools only.

BB_CreateSessionPOST

Direct cloud Chrome session for manual debugging via the live debugger URL. Capability tools do NOT need this — their Functions get sessions automatically.

BB_DeleteContextDELETE

CONTEXT-DELETE PRECONDITION, binding with or without a playbook: before invoking, obtain explicit confirmation in this conversation that names the contextId and states the consequence, which is that the saved browser state is gone permanently and cannot be recovered or re-attached; read BB_GetContext first and echo its id and timestamps so the Steward confirms the right one; never delete a context as cleanup after a capability run, because the capability Functions refuse contexted sessions and never use one. WRITE operation: DELETE \/v1\/contexts by contextId permanently and irreversibly deletes a saved browser context, meaning the cookies, localStorage and storage state that BB_CreateSession attaches through browserSettings.context for state reuse. Success is 204 with no body; 404 means the id is wrong or the context is already gone. Params: contextId (string, required, path parameter).

BB_EvaluateScriptPOST

BYOK: invokes the CALLERs own published Function via functionId (the app bakes no UUID; functions are account-scoped). Published Function evaluate-script. The Function REFUSES scripts touching credential surfaces server-side (cookie localStorage sessionStorage indexedDB navigator credentials credentialed fetch and XHR document forms value reads on any form input and getAttribute on credential-named fields) and refuses contexted sessions. No bypass parameter exists. Refusals surface as WORKLOAD_ERROR with reason in the invocation logs. Diagnostics only; SCRIPT-HYGIENE governs what may be sent. COMPLETED results carry result, console, errors.

BB_FetchPagePOST

No-browser page fetch, no JavaScript execution: cheap reachability and header checks. Redirects are NOT followed; a 301/302 statusCode in the response means re-fetch the Location target.

BB_FillFormPOST

FORM-SUBMIT PRECONDITION, binding with or without a playbook: before invoking, get explicit confirmation in this conversation naming the site, every field value and the submit control; refuse credentials, payment data and third-party personal data; prefer test targets; never create accounts, log in, message or purchase; a lost invocation id never justifies a re-fire. WRITE-SHAPED: this submits a real form on a live site, and ANY matched element that is not fillable is CLICKED instead, so a wrong selector becomes a click on whatever it matched. Verify selectors first. BYOK: invokes the published Function fill-and-submit-form in the CALLER account via functionId from BB_ListFunctions. Fields handled: native select, checkbox and radio; ARIA radio, option and menuitemradio (Google Forms) select-only; ARIA checkbox, switch and menuitemcheckbox toggled by aria-checked; text inputs, textarea and contenteditable are typed; the values 0, false, no, off, unchecked and empty un-set a toggle and anything else sets it. Returns 202 with an Invocation; poll BB_GetInvocationResult. COMPLETED results carry beforeScreenshot and afterScreenshot (bounded base64 jpeg images, null when nothing fit), screenshotFormat, screenshotsTruncated, and response (url after submit, status; a null status means no navigation followed). Params: url, fields (one entry per field, each a CSS target plus the string to enter), submitSelector, all required.

BB_GetConsoleLogsPOST

READ messagesTotal, messagesDropped, errorsTotal AND errorsDropped BEFORE STATING ANY COUNT: the arrays are returned slices, the Total keys are the real numbers, and a Dropped above 0 means that list is partial and must be reported as partial. BYOK: invokes the published Function get-console-logs in the CALLER account via functionId (the app bakes no UUID; resolve it with BB_ListFunctions first). Fresh-load console capture. Returns 202 with an Invocation; poll BB_GetInvocationResult. COMPLETED results carry messages (level, text, source, line), messagesTotal, messagesDropped, errors (console errors and page exceptions: message, stack), errorsTotal, errorsDropped. Each array is byte-bounded to about 26KB to fit the 64KB Function result cap, with text, message and stack clamped to 1000 chars and source to 512; the earliest entries are kept. Params: url (string, required), waitMs (integer 0 to 30000, always supply, 3000 unless asked).

BB_GetContextGET

Fetch a persistent browser context by id. Contexts hold saved cookies, localStorage and storage state for session-state reuse in manual debugging flows.

BB_GetInvocationLogsGET

Handler console output for a finished invocation — the diagnosis surface for FAILED runs (server-side refusals print their reason here). Verified live 2026-08-07 during the context-guard fix.

BB_GetInvocationResultGET

The poll half of every capability call: invocationId is the positional path parameter. status PENDING or RUNNING means poll again in about 5 seconds; COMPLETED carries results; FAILED carries cause (then read BB_GetInvocationLogs).

BB_GetSessionGET

sessionId is the positional path parameter. Capability invocations expose their sessionId, so this also inspects the session behind any Function run.

BB_GetSessionDebugURLsGET

RUNNING sessions only; debuggerFullscreenUrl is the live human-viewable browser.

BB_GetSessionDownloadsGET

Downloads are a top-level vendor resource filtered by required sessionId query parameter (the old per-session path no longer exists).

BB_GetSessionLogsGET

Raw CDP event log (console output, network request and response records, page lifecycle) — available only AFTER the session completes; there is no live-log endpoint. The playbook's REDACTION rule applies before presenting: never echo authorization, cookie or token values found in captured headers or bodies.

BB_GetSessionRecordingGET

Raw rrweb replay events; for a human-viewable replay prefer the dashboard URL https://browserbase.com/sessions/ followed by the session UUID.

BB_GetUsageGET

Browser-minutes and proxy-bytes; every capability invocation consumes session minutes from the same pool. Call when planning heavy runs or on request, never reflexively.

BB_InspectNetworkPOST

READ requestsTotal AND requestsDropped BEFORE STATING ANY COUNT: the requests array is the returned slice, requestsTotal is the real number, and a requestsDropped above 0 means the list is partial and must be reported as partial. BYOK: invokes the published Function inspect-network in the CALLER account via functionId (the app bakes no UUID; resolve it with BB_ListFunctions first). Live request capture during a fresh page load plus a settle window. Returns 202 with an Invocation; poll BB_GetInvocationResult. COMPLETED results carry requests (url, method, status, size, duration, type, errorText), requestsTotal, requestsDropped, and summary (total, failed, slowest, largest). The requests array is byte-bounded to about 50KB and each url is clamped to 1024 chars to fit the 64KB Function result cap; summary is computed over ALL captured requests and stays complete. Params: url (string, required), waitMs (integer 0 to 30000, always supply, 3000 unless asked).

BB_InvokeFunctionPOST

Generic invoke for any published Function in the project by its function UUID (positional path parameter). The eight capability tools above are preferred for the standard Functions; this is the escape hatch for newly published ones.

BB_ListFunctionsGET

BYOK function resolver. Lists the CALLERs own published Functions (name plus UUID) from their Browserbase account (fixed page size 100). The Mind calls this once per turn before any capability tool, maps the capabilitys function name to that accounts UUID, and passes it as functionId. If a needed function name is absent, the user has not deployed the DevTools Functions yet.

BB_ListSessionsGET

No parameters. Returns all sessions; the Mind filters by status (PENDING, RUNNING, ERROR, TIMED_OUT, COMPLETED) client-side. Bare path avoids the wrapper's optional-query-omission error.

BB_QueryDOMPOST

BYOK: invokes the CALLERs own published Function via functionId (the app bakes no UUID; functions are account-scoped). Published Function query-dom (verified live 2026-08-07). Deterministic DOM reads without arbitrary JS. No bypass parameter exists. Property vocabulary is textContent innerText boundingBox exists count visible or attribute plus a name. Credential-named attributes are blocked server-side.

BB_ReleaseSessionPOST

Ends a REST-created session early. Function-managed sessions end themselves; never call this on an invocation's session while its status is RUNNING.

BB_RunLighthousePOST

ALWAYS STATE engine AND scoresApproximate WITH ANY SCORE, and never present a local score as a Lighthouse score. Lighthouse never runs in the sandbox: engine auto (default) sends the audited URL to Google PageSpeed Insights, which runs real Lighthouse on Google servers, and falls back to an in-sandbox CDP audit on any PSI failure; a credential-looking URL is never sent to Google under auto; psi pins PSI and fails instead of falling back; local pins the in-sandbox audit and sends nothing to Google. The keyless PSI quota is shared and routinely 429s, so without psiApiKey the default usually returns the local audit. BYOK: invokes the published Function run-lighthouse in the CALLER account via functionId from BB_ListFunctions. Returns 202 with an Invocation; poll BB_GetInvocationResult, budget 5 minutes. COMPLETED results carry scores (performance, accessibility, bestPractices, seo; 0 to 100 or null), audits (worst first), auditsTotal, auditsDropped (above 0 means the audit list is partial), fetchTime, url, engine, strategy, scoresApproximate (true on local: directional only, never score-identical), note (present when auto fell back or skipped PSI), plus metrics on local and lighthouseVersion on psi. Params: url (required), categories (array, always supply), engine (auto, psi, local), strategy (desktop, mobile), psiApiKey (optional Google key; it is stored on the Invocation record and any holder of this Browserbase key can read it back, so use a key restricted to the PageSpeed Insights API).

BB_ScreenshotPOST

READ screenshotTruncated AND screenshotRenderWidth BEFORE calling an image complete or full resolution: the Function shrinks the capture to fit the 64KB Function result cap. BYOK: invokes the published Function navigate-and-screenshot in the CALLER account via functionId from BB_ListFunctions (the app bakes no UUID). Returns 202 with an Invocation; poll BB_GetInvocationResult. COMPLETED results carry screenshot (base64 jpeg, null only when nothing fit), screenshotFormat (jpeg), screenshotQuality (70 down to 10), screenshotBytes, screenshotTruncated, screenshotRenderWidth (present only when the render was narrowed, 1024 down to 360 px), screenshotNote (present when reduced), title, url. The reduction ladder is quality first, then full-page dropped to viewport-only, then a narrower render. The base64 arrives complete in the invocation result; any later loss is in attachment delivery, not here. Params: url (string, required, absolute http or https), fullPage (boolean, always supply, false unless asked). viewport is not exposed on this tool.

BB_WebSearchPOST

Web search via published Browserbase endpoint. Returns a list of search results with id, url, title. Results are filtered by the vendor; the search query is the primary signal.

Overview

Browser DevTools capabilities via Browserbase cloud infrastructure. Provides Minds with the ability to open cloud Chrome instances, navigate to any URL, capture screenshots, run Lighthouse audits, execute JavaScript, inspect network traffic, and read console output — all through Browserbase's REST API and serverless Functions. It gives your AI agent 26 built-in tools, including bb check page health, bb create context and bb create session. Apps are free to equip, and once equipped your AI Mind can use Browserbase Dev Tools Suite automatically while it works. Browserbase Dev Tools Suite is currently equipped on 60 Minds.

Frequently asked questions

What is Browserbase Dev Tools Suite?

Browser DevTools capabilities via Browserbase cloud infrastructure. Provides Minds with the ability to open cloud Chrome instances, navigate to any URL, capture screenshots, run Lighthouse audits, execute JavaScript, inspect network traffic, and read console output — all through Browserbase's REST API and serverless Functions. It bundles 26 tools your AI agent can call on your behalf.

What can Browserbase Dev Tools Suite do for my AI agent?

Once equipped, your AI Mind can use Browserbase Dev Tools Suite to bb check page health, bb create context, bb create session, bb delete context and bb evaluate script, and more — without you having to do any of it manually.

How do I connect Browserbase Dev Tools Suite to my AI Mind?

Open Browserbase Dev Tools Suite in the Ethoswarm Bazaar and select Equip to add it to one of your AI Minds. Your Mind can then use it automatically. Some apps ask you to authorize access the first time they run.

Is Browserbase Dev Tools Suite free?

Yes — Browserbase Dev Tools Suite is free to equip on your AI Mind in the Ethoswarm Bazaar.