Agtweb 0.7.0 (Firefox)

App ↔ bridge protocol stays 6.

Automation window. Tabs Agtweb opens go in a dedicated unfocused window that closes with its last tab. fork of a tab outside that window is refused. Firefox’s persistent background keeps the window across restarts.

More reliable page reads. Higher extraction budgets; oversized pages return a truncated beginning instead of failing. Long paragraphs keep full text. Assembly stops early when it would blow the step budget. Invisible CAPTCHA scripts no longer flag a challenge; short “verifying your device” pages count as blocked. Empty no-scroll grabs wait and retry once. Clock steps backward no longer abort work.

Clearer failures. ACTION_OUTCOME_UNKNOWN / PAGE_ACTION_OUTCOME_UNKNOWN end with a fixed Cause: line. The failed step stays the cause when scroll cleanup cannot confirm.

• A transient WebAssembly fetch failure no longer leaves Firefox permanently broken.
• The fork ledger repairs itself when a forked tab is closed, instead of holding a dead entry. A fork name that owns no live fork is now an error (FORK_NOT_FOUND, newly declared) rather than a silent fall-back to the wrong tab, and both killFork parameter spellings answer it.
• TAB_LOAD_TIMEOUT is correctly non-retriable on Firefox, as it already was elsewhere.
• An oversize result can no longer kill the bridge; the response producer is capped.
• Chromium: an injection argument MV3 would silently mangle is now refused outright, and an absent scroll id crosses the MV3 boundary intact instead of being dropped.
• Firefox screenshots are bounded, and the refusal is consistent across forks.

Wire protocol 4 → 6. Supersedes 0.6.0. Protocol 6 is required on both sides. Clients pinned to protocol 5 must be updated together with the extension — the bridge, the browser packages, the official clients and the Safari path all move at once.