# Backlog

Things that are wanted later and are deliberately not scheduled. Nothing here has an issue or a phase. When one is picked up, it gets an issue and moves out of this file.

## Firefox and Safari (decided 2026-10-15: not yet)

Alex's call: backlog these for a while; Chrome only for now.

What is known, so the work does not start from zero:
- The extension is Manifest V3 for Chrome. The engine, parser, bundle and archive code (`runner/`, `shared/`, `extension/worker/`) use WebCrypto and plain web APIs and are not Chrome specific; the Chrome specific parts are `extension/src/` (tabs, scripting, alarms, storage) and `extension/worker/extensionCdp.ts` and `extensionDownloads.ts`.
- Real input, screenshots and network idle go through `chrome.debugger` in the worker. Firefox has no equivalent of `chrome.debugger`; Safari's extension model is further still from it. A port would need another way to get trusted input (or accept synthetic page events, which the plan marks as weaker), so this is a design question and not only packaging.
- Chrome for Testing is pinned and the self-check runs against it; another browser needs its own pinned build and fixture run.

## Documented elsewhere as set aside
See `docs/PLAN.md` section 12 (hosted multi-user dashboard, mobile browsers, load testing, visual diffing, bug tracking) and decision D2 (a Playwright backend for OS prompts, virtual passkeys and headless signed-in CI).