AceAtDev/ascended-browser

A real browser for your AI agent. One command to add.
A local, open-source browser MCP server for Codex CLI, Claude Code and other
MCP clients. Use it for interactive browser automation and front-end QA:
inspect console logs and network requests, check responsive layouts, and
collect screenshots alongside what happened on the page.
Your agent opens pages, reads
them, and acts on them through verified actions: it fills a whole form in
one call, picks "Mrs." from a custom React dropdown by name, and is told what
the page did in response, instead of clicking coordinates and hoping.
Ascended is my own private agent workspace; this package extracts its browser
so it can run on its own:
Camoufox (a hardened Firefox that looks like a
person's browser to the sites it visits) behind the same tool dispatcher, page
reading and result formatting Ascended's own agent uses.
## Start with a QA check
Read the documentation site:
QA setup and
interrupted-action reproduction.
Running Codex CLI over SSH and missing a browser? Connect a browser MCP on your Linux dev box with setup commands, localhost guidance and alternatives.
Practical recipes with real local-fixture screenshots:
Find console errors and failed requests.
Check responsive layouts.
Test login-protected pages and session reuse.
Set up a browser MCP for Codex CLI or Claude Code and check your app.
The guide covers installation, a copy-paste QA prompt, console and network
inspection, bug-report structure, and what to do after an interrupted action.
Check a local app: walk through a flow and report errors before changing code.
Inspect the evidence: read failed requests and console errors, then capture the broken state.
Use a Linux dev box: run the client, MCP server and app on the same machine;
the guide explains how localhost behaves when you connect over SSH.
This is agent-assisted exploratory QA, not a replacement for deterministic
regression tests or a validated CI integration. Browser MCP tools are also
available from projects such as Playwright MCP and Chrome DevTools MCP;
console and network inspection are not exclusive to this server.
## See it work
Three real runs of Claude Code with only this server attached, on live sites.
The panel on the side is Claude Code's own transcript: every tool call it made
and what came back, errors included, with the real elapsed time. Waiting is
cut and tool time plays faster; the pointer, device frames, devtools panels
and outlines are drawn afterwards from the server's event log
(demo/recorddemo.py), so they sit on what the agent really touched and read.
The full unedited screen recordings are in videos/unedited/
(the browser is driven through Playwright, so no OS pointer appears in them).
Front-end QA. react.dev on a phone and a tablet, dark/light, before/after screenshots, an audit outlining the real offending elements, console and network.
Browsing. Types into Wikipedia's search, finds a fact in the article, then searches YouTube and plays the first video.
Real forms. booking.com: popup, destination autocomplete, date picker, search, sort by price.
Saved logins. You save a login once; the agent signs in with it and never sees it. Built from a real run (demo/logindemo.py, then demo/loginexplainer.py): the CLI's output, the screen, and the exact text and pictures the agent got back.