Repository navigation
test(computer-use): bake-off subcommand for background Chrome - #39
Merged
Merged
Conversation
node scripts/computer-use-dev.ts bakeoff serves a small page that logs every DOM event with isTrusted, opens it in a background Google Chrome with its own profile, runs 11 tasks through computer_action over MCP, and prints a pass/fail table with response sizes, delivery paths, and whether the user's pointer or front app moved.
maschwenk
marked this pull request as ready for review
November 9, 2026 01:12
This was referenced Nov 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
the chrome bake-off from today lived in /tmp and drove the native worker over stdio, so it never went through the mcp layer agents actually use. this makes it a subcommand of computer-use-dev.ts so the next computer use prs (the shared verbs one is stacked on this) all run the same check
node scripts/computer-use-dev.ts bakeoff(add--home .t3for a worktree dev server)what it does
scripts/computer-use-bakeoff.htmlon a loopback port. the page posts every dom event back withisTrustedand where it landed--disable-backgrounding-occluded-windows+--disable-renderer-backgrounding, otherwise a covered chrome stops painting), puts the front app back if the launch grabbed it, and quits chrome by the pid whose command line names that profileNSEvent.mouseLocation+ the front app are the same before and after every callvia, resultbaseline on main (88cb172, has the input, diff and cursor prs) with a dev server started from this worktree. 3 runs in a row came out identical except list scroll moving by a few chars
11/11, first snapshot 5758 chars, my pointer and helium in front never moved
worth knowing
hover, move away and scroll come back around 4.2k chars. the diff isnt broken: showing the hidden button makes its row 3 px taller, so every element below gets a
~line for its new y, including 40 clipped list rows. scroll moves every list row the same way. codex is 125-580 per action, so bounds churn is the next thing to look at for sizethe first button click goes through a pointer event, not ax press. chrome doesn't list
presson web elements in the first snapshot after launch (the diffs pr saw this too). the revealed button later on goes through accessibilityhover only passes because my real cursor sits inside chrome's window area (818,749 in cocoa coords vs a window at 40,40 900x1000). thats the known limit from the background input pr, and the summary line prints the pointer so you can tell
the chrome profile stays in the temp dir between runs. a managed 1password extension opens a welcome tab on a fresh profile, once 20 s after launch, and that ate a step. so the script closes any other tab before each task, and keeping the profile means it only happens on the first run
a dev server started from a t3 code (fork) terminal has accessibility + screen recording, macos credits the app that started the shell. so no dev electron app needed, runbook says so now
docs(computer-use): one vocabulary for apps and browser tabs #38
fix(computer-use): hover, exact click_at and real typing in background apps #37
perf(computer-use): computer_action returns what changed, not the whole tree #36
written by claude opus 5.5 in claude code