Document per-type captcha telemetry coverage

[archandatta]

Summary

• add a table to the telemetry categories page listing, per captcha_type, whether task events, captcha_challenge_result, and challenge_id on task events are emitted
• state which challenge statuses each observed type reports: solved or abandoned for recaptcha_v2 and hcaptcha, plus failure and timeout for press_and_hold
• add GeeTest and hCaptcha-configuration bullets to the Limits section of the pausing-for-captcha-solves cookbook, matching the existing press-and-hold note

Why

The cookbook's page probe has no GeeTest selector or token field, so a developer following it on a GeeTest page gets a gate that lets the agent proceed while the challenge is still open. The Limits section only called this out for press-and-hold. The coverage table replaces the one-sentence summary so readers see the per-vendor differences before building on them.

The challenge_id column says "Can be absent" rather than "No" for the solver-only types because that identifier is being added to more task events upstream, and the docs should not need a second edit when it lands.

Testing

• text-only change; no local render

The hCaptcha bullet states that solver availability is configured per organization. Drop that bullet if this should not be public.

🤖 Generated with Claude Code

---

Note

Low Risk
Documentation-only updates to captcha telemetry and cookbook limits; no runtime or API behavior changes.

Overview
Telemetry categories now includes a per-captcha_type table for task events, captcha_challenge_result, and whether challenge_id appears on task events (with “Can be absent” where upstream may add it). It also states which challenge statuses each type reports: solved/abandoned for reCAPTCHA v2 and hCaptcha, and failure/timeout for press-and-hold.

Pausing for captcha solves adds two Limits bullets: GeeTest gets task telemetry but the cookbook PROBE has no GeeTest widget/token checks, so the gate may release early; hCaptcha events only appear when the org has the hCaptcha solver enabled, otherwise the gate falls through to the page probe.

^{Reviewed by Cursor Bugbot for commit cf0bad9. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
Kernel	🟢 Ready	View Preview	Sep 23, 2026, 6:58 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

[cursor]

Risk level: Very Low

Approved. This pull request only adds prose to two Mintlify docs pages:

• browsers/telemetry/categories.mdx — a coverage table and one sentence on which challenge statuses each captcha_type reports (+14)
• browsers/telemetry/pausing-for-captcha-solves.mdx — two Limits bullets on GeeTest selectors and org-level hCaptcha solver coverage (+2)

No application code, config, API, auth, infrastructure, or docs.json changes. The repo has no CODEOWNERS file, and this PR has no prior approval. The added text is user-facing documentation, not model instructions or production logic.

  

_{Sent by Cursor Automation: Assign PR reviewers}