stitch::extract-static-html

Topics in the source

• Extract Static HTML
• Which Strategy to Use
• Strategy A: Puppeteer Snapshot (Recommended)
• Prerequisites
• Workflow
• Script Flags
• What It Does Automatically
• Framework Notes

Extract a self-contained static HTML file from any web application. You MUST ask the user to choose which strategy to use before proceeding. Present the options clearly, recommend Strategy A as the preferred default, and provide a brief pros/cons summary for each option to help them make an informed decision. | | Strategy A (Puppeteer) | Strategy B (Browser Subagent) | | :--- | :--- | :--- | | When | App runs locally, no auth wall | Need to interact with page first (click, fill forms) | | Fidelity | Highest — computed styles resolved | High — rendered DOM | | Setup | Zero — no mock needed | Zero — no mock needed | | Framework | Any | Any | | Output | Writes to file — no size limit | May truncate in agent context | [!WARNING] Checkpoint — User Confirmation Required. You MUST ask the user which strategy they prefer before proceeding. Present the comparison table above, recommend Strategy A as the default, and wait for explicit approval. Do NOT make the decision yourself or proceed until the user confirms. Launches headless Chrome, captures the fully rendered DOM, and produces a self-contained HTML file with all CSS inlined and images as base64. Works with any framework — no MockPage.

This is an excerpt. Refer to the complete source and its current requirements.