Public Browser
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHROME_PATH | No | Path to Chrome binary (overrides auto-detection) | |
| SILBERCUE_CHROME_PORT | No | CDP debugging port | 9222 |
| PUBLIC_BROWSER_PROFILE | No | Chrome profile name or path to use | |
| PUBLIC_BROWSER_TELEMETRY | No | Opt-in: upload anonymised Cortex patterns to the community endpoint | |
| SILBERCUE_CHROME_PROFILE | No | Chrome user profile directory (auto-launch only) | |
| SILBERCUE_CHROME_HEADLESS | No | Opt-in headless mode for CI/server environments | false |
| SILBERCUE_CHROME_AUTO_LAUNCH | No | Auto-launch Chrome if no running instance found | true |
| PUBLIC_BROWSER_TELEMETRY_ENDPOINT | No | Override the telemetry collection endpoint (must be HTTPS) | https://cortex.public-browser.dev/v1/patterns |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| virtual_deskA | List all open tabs with IDs, URLs and state. Call it first in every session, after a reconnect, or when unsure; reuse a listed tab ID instead of opening duplicates. Cheap, call liberally. |
| view_pageA | See what is on the page: text plus stable element refs for click/type/fill_form. Default filter 'interactive' lists actionable elements; for paragraphs or table cells call view_page(ref, filter: 'all'). Collapsed containers show as [eXX role, N items] — expand with view_page(ref: 'eXX', filter: 'all'). |
| clickA | Click an element by ref, CSS selector, visible text, or viewport x/y (canvas, pixel-precise targets). Dispatches real CDP mouse events. A click that opens a new tab is reported in the response. The DOM diff (NEW/REMOVED/CHANGED) arrives with the next page action, or here with wait_for_diff: true. |
| typeA | Type text into an input identified by ref or CSS selector. For 2+ fields use fill_form; for special keys (Enter, Escape, Tab, arrows) or shortcuts (Ctrl+K) use press_key. |
| fill_formA | Fill a whole form in one call: text inputs, (by value or visible label), checkboxes (boolean) and radio buttons. One round-trip; partial errors do not abort and each field reports its own status. On per-field errors call view_page and retry the failing fields. |
| press_keyA | Press a key or shortcut (Enter, Escape, Tab, arrows, Ctrl+K). Optionally focus an element first via ref or selector. |
| scrollA | Scroll the page, a container, or an element into view. Reports the position and content growth (scrollHeight delta — detects lazy-loaded content) and handles settle timing. Use container_ref/container_selector plus direction to scroll inside a container. |
| dragA | Drag a source onto a target: HTML5 drag-and-drop (draggable lists, SortableJS, React DnD) and mouse drags (sliders, canvas, resize handles). Scrolls the source into view; says when no page reaction was detected. Source: from_ref/from_selector or from_x+from_y; target: to_ref/to_selector or to_x+to_y. |
| navigateA | Navigate the active tab to a URL, or action 'back' / 'reload' (all refs become stale after reload). Waits for settle. Overwrites the user's active tab — check virtual_desk first; the first call per session is redirected to virtual_desk. |
| switch_tabA | Open a new tab, switch to a tab by ID (from virtual_desk), or close one. Prefer 'open' over navigate when the user's active tab must stay untouched. Refs from the previous tab are invalid afterwards — call view_page before acting. |
| tab_statusA | Active tab's cached URL, title, ready state and errors — a cheap mid-workflow sanity check ('did my click navigate?'). Not for tab discovery or page content. |
| wait_forA | Wait until a condition holds: element visible, page text present, URL match, network idle, or a JS expression true. Prefer condition 'text' over a JS expression for 'has the page said X yet'. assert: true checks once and fails instead of waiting. |
| observeA | Watch an element for changes instead of polling with MutationObserver/setInterval code in evaluate. collect: record text/attribute changes for 'duration' ms. until: wait for a condition, then optionally click at once (then_click). click_first fires the triggering action after the observer is armed, so nothing is missed. |
| capture_imageA | Pixel-level screenshot (WebP, max 800px, <100KB). Only for canvas or chart content without DOM text, pixel-level rendering or animation checks, or when the user explicitly asks for a screenshot. Returns no refs and reads no text — that is view_page. |
| dom_snapshotA | Structured layout data: bounding boxes, computed styles, paint order, colors; refs match view_page. Only for spatial questions view_page cannot answer (is A above B? what color?). |
| handle_dialogA | Configure handling of alerts, confirms and prompts. Set it BEFORE triggering the action that opens the dialog. Uses CDP Page.javascriptDialogOpening, so it works even while the dialog blocks all JS. |
| file_uploadB | Upload file(s) to an identified by ref or CSS selector; file paths must be absolute. |
| console_logsA | Read collected browser console logs; filter by level (info/warning/error/debug) and/or regex; optionally clear the buffer after reading. |
| network_monitorA | Capture network requests via CDP, including those the page issues itself. Workflow: start → trigger the action → get(pattern: 'api'). |
| downloadA | Wait for pending downloads or list this session's downloaded files. Downloads start by themselves when you click a download link or open a file URL (PDF, CSV, …); this tool never triggers them. download() waits for a pending download to finish; download({ action: 'list' }) returns at once. |
| configure_sessionA | View or set session defaults for recurring parameters (tab, timeout, …). Without params: show current defaults and auto-promote suggestions; autoPromote: true applies them. Set profile BEFORE any browser interaction to launch Chrome with a named profile. |
| run_planA | Batch the next 2+ known actions (click, type, scroll, view_page chains) here instead of N separate calls: a sequence of tool steps, executed server-side in one call. Variables via vars and saveAs ($name), conditions (if), suspend/resume to ask the agent mid-plan, and errorStrategy abort | continue | capture_image. |
| batch_evaluateA | Visit several URLs in sequence and run the same JS expression on each. For controlled checks across known pages where view_page/run_plan would be too chatty; not for normal reading, clicking or form work. |
| set_page_dataA | Write a payload larger than 1 MB into window.__pb_data[key], chunked past the CDP 1 MB message limit. Source: inline ( |
| evaluateA | Run JavaScript in the page. Good uses: computation, style mutations (.style.X = ..., classList), shadow-root traversal, in-page fetch(), app-specific side effects no dedicated tool covers. Scope is shared between calls; top-level const/let/class are wrapped in an IIFE. If/else blocks may return undefined — use a ternary or an explicit return. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 25 tools
Each tool has a clear, singular purpose with minimal overlap. view_page and dom_snapshot are distinct (text/refs vs layout/geometry), and capture_image is explicitly limited to pixel-level content. The descriptions reinforce boundaries, so an agent should rarely misselect.
The majority follow a verb_noun pattern (view_page, file_upload, fill_form, switch_tab), but there are single verbs (type, click, scroll, evaluate) and noun-only names (virtual_desk, console_logs). The consistent snake_case and predictable verb-first style keep it readable, though not perfectly uniform.
At 25 tools, this is on the heavy end of the appropriate range. However, each tool addresses a distinct browser automation capability (navigation, interaction, waiting, dialogs, downloads, JS execution, network, etc.), so the count is justified by the breadth of the domain.
The surface is remarkably complete for browser automation: navigation, tab management, clicking, typing, forms, drag-and-drop, scrolling, waiting, dialogs, downloads, screenshots, DOM inspection, JS execution, network monitoring, console logs, file upload, session config, and batch evaluation. No critical gaps are apparent.