MCPlexer
The control plane Revitt uses for serious agent work: task state, skills, memory, secret-safe tool calls, browser automation, and routed MCP access.
Open MCPlexeropen source by Revitt
Revitt's public bench for MCPlexer, Brw, and the small operating skills that make agents useful in logged-in, messy accounts.
products
The first Don Works drop is the operating layer Revitt uses while building systems: MCPlexer for routed tools and state, Brw for browser work, and the launch notes that make the next run faster.
The control plane Revitt uses for serious agent work: task state, skills, memory, secret-safe tool calls, browser automation, and routed MCP access.
Open MCPlexerChrome automation that works where launches actually happen: logged-in tabs, semantic actions, screenshots, stale refs, and outcome checks.
Open BrwThis site, the launch path, and the first website-ops skill pack for Cloudflare, Vercel, and 123-reg setup runs.
Open site repobuilt here
Don Works should read like a bench with real parts on it: product repos, launch notes, and the weird operational details that usually get lost.
Tasks, skills, memory, Telegram updates, browser control, routed MCP tools, and audit all sit behind one operating layer.
It finds logged-in Chrome tabs, reads awkward dashboards, clicks through vendor flows, and verifies the result without pretending the web is clean.
Cloudflare, Vercel, and 123-reg notes capture the weird bits: hidden tabs, stale refs, nameserver panels, Domain Connect, and final DNS checks.
signal
MCPlexer gives agents a serious operating layer. Brw gives harnesses the browser automation they need for real accounts, real tabs, and real verification loops. The repos are public; the runbooks follow the work.