Troubleshooting generation issues

The common failure modes and what to do about them.

"That doesn't look like a valid URL"

The command bar needs a plausible public hostname (example.com, https://linear.app). Local addresses, internal IPs, and non-HTTP schemes are rejected before any work starts - and cost nothing.

The site can't be analyzed

Some sites block automated browsers. Symptoms: the generation fails during extraction, or the output notes a limited read. Options:

  • On Pro or Max, use a screenshot of the site instead - screenshot-only mode needs no crawler access.
  • Try a different page on the same site; blocking is often path-specific.

The output says "Approximate" or "partial"

That's the honesty system working. When a site exposes little CSS to read (heavy JavaScript rendering, blocked stylesheets), Mateo flags the affected values instead of presenting estimates as facts. A screenshot-only run always carries the "screenshot-only" flag.

A generation seems slow

Typical runs are 40–100 seconds; visually rich sites sit at the top of that range because there is genuinely more to specify. Screenshot-only runs skip the crawl entirely and are usually the fastest.

The document is missing later sections

Extremely rich sites can hit the output length ceiling. The result flags this with a notice - regenerating usually completes the document.

You've hit your monthly limit

The account menu shows usage and the exact reset time. Upgrading takes effect immediately - see plans and quotas.

Still stuck? Contact support - include the URL or input mode, what you expected, and roughly when it happened.