Repository navigation
Limitations
Mustapha Zoghlami edited this page Nov 4, 2026
·
1 revision
BrowserForge reports what a WebExtension can actually see; it does not capture all browser traffic. Highlights:
- Firefox cannot observe WebSocket frames; Chrome can only through the "bodies" build and the
debuggerpermission (issue #12). -
Iframes are read and driven (up to 12 child frames per call); sandboxed frames and
file:pages are skipped. - Open shadow roots are read and driven; closed shadow roots are invisible (#11); recorded locators inside shadow roots cannot be replayed yet (#10).
- Consequential-action detection is heuristic: it errs on the side of asking you.
- Flows only know elements BrowserForge could see (no canvas apps); a redesigned site needs a new recording.
- The local models see a table of at most 100 visible controls, not screenshots; always verify the result.
- Everything has been run by hand only on Linux; Windows and macOS are exercised by CI (#5).
The full, current list: docs/LIMITATIONS.md.
MIT licensed · Repository · Issues · Releases · Privacy
Use it
Grow it
Trust it
Help
Project