Current URL
The exact route, query string, and page the developer is viewing.
AI browser debugging
AI browser debugging: Give agents DOM and console context.
Give the agent the rendered page, DOM context, console evidence, failed loads, screenshots, and the source code that produced the problem.
Browser evidence beside the codeSend the current page to AI without reconstructing its state in a prompt.
The problem
A symptom is not enough context.
Copying one error and attaching one screenshot leaves the agent guessing about the route, viewport, selected element, console state, and failed resources.
Browser-aware debugging replaces that guesswork with evidence the agent can inspect and verify against the source.
The context packet
Send the evidence that changes the diagnosis.
Rendered content
Visible page text and HTML context, not only the source template.
Console evidence
Fresh logs, uncaught errors, warnings, and runtime stack frames.
Failed loads
Resources and requests the page could not load successfully.
Visual state
A viewport, full-page, or selected-element screenshot when appearance matters.
Project context
The repository, active worktree, terminals, and uncommitted source behind the page.
Closed-loop debugging
A fix is complete when the browser agrees.
Keep diagnosis, implementation, and verification in the same workspace.
- 01
Open the failing state
Run the app in Flame's internal browser beside its source and project terminals.
- 02
Capture browser evidence
Send the URL, console output, errors, failed loads, and an optional viewport or element screenshot to AI.
- 03
Inspect the live page
Let the permissioned agent inspect rendered content, fresh console logs, screenshots, and page state.
- 04
Fix the source
Map runtime symptoms and stack frames to the repository files that implement the page.
- 05
Verify in the same browser
Reload, check the console again, and compare the rendered result before declaring the issue fixed.
Visual verification
Compare pixels and rendered DOM.
Browser Compare places two pages side by side, measures visual mismatch, overlays differences, and identifies rendered DOM changes.
For parallel frontend tasks, combine browser verification with isolated agent worktrees so every candidate can be run and reviewed independently.
Browser CompareMeasure what changed instead of relying on a quick visual check.
Two browser paths
Use the internal browser by default. Connect Chrome when the real profile matters.
Internal browser
- Local previews beside the repository
- Page context, screenshots, and console evidence
- Agent-driven reload and verification
- Reproducible browser sessions for development
Chrome Browser Bridge
- Optional access to your existing Chrome profile
- Separate pairing and explicit tab permissions
- Useful when authentication or browser state matters
- Designed for approved, task-specific access
Product walkthrough
Watch a visual bug move from browser evidence to code fix.
Official Flame demo
Visual Bug Fixing with Built-In Browser + AI
See Flame capture the live page and selected element, give that evidence to the coding agent, and reload the result in the same browser.
FAQ
AI browser debugging questions
Give the agent the page, not a paraphrase.
Download Flame and debug with live browser evidence beside the code that produced it.
Free to use on macOS, Windows, and Linux.