back
Navigate back in browser history
LABSCO SUMMARY
The reproduction survives the session that produced it.
browser_generate_playwright_test turns the clicking-around into code, so a bug reproduced once becomes a test that reproduces it every time afterwards, rather than a paragraph describing what someone did. The console messages and network requests come from that same session, which means the evidence and the repro are the same run instead of two attempts that may not match.
What it is
A browser automation server built on sessions: 29 tools covering launch, navigation, interaction by CSS selector, dialogs and tabs, screenshots and PDF, network and console capture, and Playwright test generation.
What you get
- Sessions launched headed or headless, with viewport, timeout, screenshot quality and compression chosen at launch
- Interaction by CSS selector: click, type, hover, drag between two selectors, key press, dropdown select and file upload
- Waiting on a selector, plus three readings of the page — accessibility tree snapshot, HTML content and visible text
- Navigation and tabs: back, forward, refresh, resize, and new, list, select and close for tabs
- Dialog handling for alert, confirm and prompt, with the prompt text supplied
- The page's own record of the session: every network request and every console message
- Playwright test code generated from the actions recorded in that session
Requirements
npx on your PATH, and the sessionId returned by browser_launch, which every subsequent call takes. No account, no key.
Setup effort
One command — npx @snowfort/circuit-web@latest
USE CASES
01
Reproducing a bug a user reported
Launch a session, go to the page, and walk the steps the report describes. Running headed makes the failure watchable; a screenshot at the moment it happens makes it attachable.
02
Turning that reproduction into a regression test
Generate Playwright code from the actions already recorded in the session, so the steps you just performed become a file in the repository rather than a comment describing them.
03
Finding out why a page renders wrong
Pull the console messages and the network requests from the same session that showed the problem, then read the HTML the page ended up with — the three together separate a failed request from a script error from bad markup.
04
Filling in and submitting a form
Type into the fields, choose from the dropdowns, attach the file the form asks for, and wait on the selector that only appears once the submission succeeded, so the check is on the result rather than on a timer.
05
Capturing a page for someone who will not run the browser
Resize to the viewport in question, screenshot it, and export the whole page as a PDF — enough for a review or a bug report that has to travel without a session behind it.
29 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
browser_console_messages
Get all console messages from the session
browser_generate_playwright_test
Generate Playwright test code from recorded actions
browser_handle_dialog
Handle browser dialogs (alert, confirm, prompt)
browser_launch
Launch a new browser session
browser_navigate
Navigate to a URL in an existing browser session
browser_network_requests
Get all network requests from the session
browser_resize
Resize browser window viewport
browser_tab_close
Close a tab by ID
browser_tab_list
List all open tabs
browser_tab_new
Open a new tab
browser_tab_select
Select a tab by ID
click
Click on an element identified by a CSS selector
close
Close a browser session
content
Get the HTML content of the current page
drag
Drag an element to a target location
evaluate
Execute JavaScript in the page context
forward
Navigate forward in browser history
hover
Hover over an element identified by a CSS selector
key
Press a keyboard key
pdf
Save the current page as a PDF
refresh
Refresh the current page
screenshot
Take a screenshot of the current page
select
Select an option from a dropdown
snapshot
Get accessibility tree snapshot of the current page
text_content
Get the visible text content of the current page
type
Type text into an element identified by a CSS selector
upload
Upload a file to an input element
wait_for_selector
Wait for an element to appear on the page
BEFORE YOU INSTALL
What to know first
Tools you get
29 tools when we connected. This covers the web server, @snowfort/circuit-web. The desktop server, @snowfort/circuit-electron, is separate and adds tools such as app_launch, ipc_invoke and fs_write_file.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 29 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"circuit-web": {
"command": "npx",
"args": [
"@snowfort/circuit-web@latest"
]
}
}
}npx
TERMINAL
npx @snowfort/circuit-web@latest
