Inspect and debug browser pages from an Ace channel
A pull request for this has already been merged.
- #163 by @iamnbutler — merged
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- developer-experience
Research direction
Start with docs/browser-tools.md (documented by merged PR #163, commit 8ae23e4) and the implementations of browser_tabs, browser_navigate, and browser_inspect to learn the channel/host boundary and how tools return through the history path. Then pick one unchecked acceptance item — DOM input with element references, console/network inspection, or managed browser launch/lifecycle — since each is a self-contained slice. Done means the new tool behaves like #163's: bounded text/images, honest failure messages, no replay after interruption, and a walkthrough from a native Ace channel.
Written by the indexing model from the issue text.
Description
Ace development used browser DOM/accessibility snapshots, interaction, screenshots, uploads, console/network inspection, and responsive checks. githubnext/desktop-tools#11 explicitly covers native browser Accessibility/pixels; DOM/browser-session integration needs its own capability.
Acceptance
- Select an explicit browser and tab on the execution host; navigate, inspect DOM/accessibility, interact, and capture screenshots. #163: exact tab selection, navigation, main-frame accessibility and viewport screenshots landed. Remaining: DOM input (click, fill, keys) with element references, DOM inspection, and iframe content.
- Inspect console errors and failed network requests; support file upload, viewport changes, and mobile/touch emulation used in the reviewed work. Remaining.
- Keep the browser target identifiable across reconnects. Local and hosted execution must target the execution machine, not the viewing client. #163: exact browser-instance and tab targets, execution-machine routing for local workers and workspace
Link/serve, and refusal of replaced browsers. Remaining: managed launch and lifecycle of the dedicated browser, and a deployed hosted-object check. - Return bounded text/images and actionable failures through the existing channel tool/history path. Done for githubnext/ace#163's tools; required for each remaining capability.
- From a native Ace channel, reproduce a real web UI defect, inspect its cause, fix its lane, and verify the result with retained evidence. Remaining.
Use an appropriate browser backend; external harness integration is not required. Follow the existing channel/host boundary, pi history ownership, and collaborator-agent switch.
Status
First slice landed in githubnext/ace#163 (8ae23e4, documented in docs/browser-tools.md): browser_tabs, browser_navigate and browser_inspect for Ace's dedicated loopback browser, with honest navigation outcomes and no replay after interruption. GitHub closed this issue automatically when githubnext/ace#163 merged because the PR was linked as closing it; githubnext/ace#163 itself says it doesn't close githubnext/ace#50, and the acceptance above isn't met. The Browser Preview tab is the separate channel preview surface in githubnext/ace#16.
Dogfooding MVP: githubnext/ace#5. Related: githubnext/desktop-tools#11, githubnext/ace#16. Review evidence.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from githubnext/ace2
-
Difficulty 1/5 Under an hour Newbie friendliness 94/100
githubnext/ace2#487 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
githubnext/ace2#486 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
githubnext/ace2#459 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
githubnext/ace2#437 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
githubnext/ace2#442 ·
Similar issues
-
[测试] 等待仓库加载后再记录多仓库排序基线Possibly taken @myot233 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
area:arcade p3-medium ready-for-agent testing type:docs
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
fderuiter/deruiter.dev#2369 ·
Maintainers usually reply within 1 day
-
area:devenv origin:agent type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
overengineeringstudio/effect-utils#1949 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
ccch1mneyyy/dsh-TUI#1631 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
MiniMax-AI/minimax-code#507 ·
Maintainers usually reply within 1 day