Cloudflare's Precursor watches for agents that look like browsers

Cloudflare announced Precursor on 13 July 2026. It is a continuous behavioural validation engine for bot management, and the idea behind it is easy to state: stop judging a visitor by one checkpoint and start judging the shape of the whole session. Cloudflare's own announcement places it inside Enterprise Bot Management and describes it as complementing Turnstile rather than replacing it.

The problem it aims at is real. Modern automation can execute JavaScript, drive a real browser and clear an individual CAPTCHA. What is harder to fake is behaving like a person for the length of a visit.

What Precursor actually watches

Cloudflare injects a client-side script that collects behaviour and evaluates it at the edge across the session, rather than at one page view. Cloudflare's description is specific about the inputs and quiet about the thresholds, which is normal for a detection product.

• Pointer movement and keyboard timing, correlated over a session rather than a single request.

• Focus changes and page visibility, which separate a session someone is using from a script that renders a page and leaves.

• Aggregated telemetry, which Cloudflare says is privacy-preserving rather than a recording of what people type.

That last point is a design claim, not an audit. It is the claim to hold the product to if you deploy it, and the one to read the documentation for rather than a launch post.

Where it sits beside Turnstile

These are different products answering different questions. Turnstile asks a visitor to prove something once, at a point you choose. Precursor watches what a session does over time. Cloudflare presents the second as complementing the first inside Enterprise Bot Management; it is not a replacement for the challenge.

The release status is worth checking rather than assuming. Cloudflare's press release of 13 July 2026 describes Precursor as generally available. Cloudflare's own documentation, as quoted by InfoQ's analysis of 8 August 2026, describes it as an open beta that stays free until general availability. Both are Cloudflare's words. If the distinction matters to your rollout, check your account's current status rather than a summary, including this one.

What this means for a Form

FormFlow does not use Precursor. Turnstile is the challenge FormFlow offers, and it is one provider's challenge: FormFlow fails open, so when Turnstile cannot be reached, a Submission is not blocked on that basis. The spam judgment is a separate layer. FormFlow weighs request evidence against a per-Form model trained from human Corrections, and a Team prior can flag a Submission but never veto it.

Read together, those are three different layers: a challenge, a behavioural product you might put in front of a whole site, and a Form's own spam judgment. None of them is a guarantee, and none of them is a substitute for the others.

What this does not decide

Precursor does not decide whether a visitor is a bot. It produces a signal for a policy you configure, and the policy is where the decision lives.

It does not replace Turnstile, and Cloudflare does not present it that way. It does not by itself make agent traffic unlawful or unwelcome, and it does not tell you what your own terms of service should say about agents. A detection score is not a rule.

It is not a FormFlow feature, and nothing here says FormFlow will adopt it. For the mechanics a Form does have, read the API reference and the v1.0.0 Changelog entry.