Limits
Where an agent scan stops, and why each one is where it is.
Chrome's debugger banner. Every scan shows it, for as long as the scan takes. It is Chrome's notice, not ours, and an extension cannot suppress it. Unattended, it will appear without you having asked for it.
A tab with DevTools open cannot be captured at all. Only one debugger can attach to a tab at a time. Close DevTools, or scan a different tab.
No raster fallback. When the extension is driven by a click and the debugger cannot attach,
it falls back to scrolling and stitching screenshots. That path needs activeTab, which only a
real click grants, so an agent scan of a page the vector capture cannot handle fails loudly
rather than quietly handing back something worse.
chrome:// pages, the Web Store, other extensions' pages and the PDF viewer are off limits
to any extension.
The crop is always the whole page. An agent has no preview to crop against.
Hyperlinks are not preserved as links in the PDF. The text is real; the links are not.
A page past 60,000 CSS pixels a side is captured up to that limit, and the result says so in
truncated rather than passing for a whole page.
One pairing per machine, shared by every browser profile that connects to it.