Refresh & limits

Cadence

Each managed site refreshes on a cadence you choose:

• Weekly (default) — right for most docs and marketing sites, which don't change daily.
• Daily — for sites that update often.

A scheduled job checks due sites and regenerates them. You can also hit Regenerate in the dashboard any time to force an immediate rebuild.

Smart change detection

A refresh doesn't blindly rebuild. We first take a cheap fingerprint of your site (its sitemap, falling back to the homepage). If nothing has changed since the last build, we skip the full crawl + regeneration — your file stays as-is and no webhook fires.

This means:

• A daily site that rarely changes costs almost nothing and won't churn your file.
• When content does change, the next refresh picks it up and (if set) calls your webhook.
• At least every 30 days we do a full rebuild regardless, so nothing drifts stale.

Limits by plan

"Refreshes / mo" counts only full regenerations (when content changed or the 30-day rebuild is due) — the cheap no-op checks above don't count against it. If you reach the cap, your site keeps serving its last generated file until the next month or an upgrade.

"llms-full.txt pages" is how many documentation pages get inlined into a managed site's llms-full.txt. Sites with fewer pages include everything they have; larger sites are covered up to the cap, documentation-first.

Forcing a rebuild

Click Regenerate on a site to rebuild immediately, even if the content looks unchanged — useful right after you've edited the site or its instructions. Manual rebuilds aren't charged against your monthly refresh count.

Pausing

Toggle a site inactive (in Edit) to stop scheduled refreshes without deleting it. Its hosted files stop being served while paused.