No server code. Astro sites deploy through an adapter, and the agent goes where the adapter runs: the Vercel middleware, a Netlify Edge Function, or a Cloudflare Worker.
Astro sites deploy through an adapter, and the agent goes where the adapter runs: the Vercel middleware, a Netlify Edge Function, or a Cloudflare Worker. A fully static Astro build on any host can still sit behind a Cloudflare Worker.
What it does not: without a place to run, the agent cannot count visits or apply switches on this host — put a Cloudflare Worker in front of it, or move the domain to a host with middleware.
How installing the agent works, in general → · what the agent does and never does →
No. Installing puts the agent in place and binds it to the site by its token; nothing is applied. Every switch is your click in the dashboard and every word it writes is shown to you first.
Remove the file and redeploy. Whatever was last switched on stops being served on the next request. Your checks and the agent's memory stay in your Reflexa account.
The 23 checks run from outside on every page check. The free tools read the site the way AI does. Without a place to run, the agent cannot count visits or apply switches on this host — put a Cloudflare Worker in front of it, or move the domain to a host with middleware.
Yes — it belongs to this one site and should live in an environment variable, never in a file you commit. It grants nothing beyond this site, and the domain proof refuses it from any other host.
The 23 checks run from outside before anything is installed — you see what the agent would do before it does it.