Fix CAPTCHA callback delivery and post-solve recovery - #3117
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
added 2 commits
September 30, 2026 11:38
added 2 commits
September 30, 2026 11:48
Models routinely fill the optional callback object with schema placeholders
like `{ name: '', path: '' }`. Those bindings used to fail validation and
request the EXECUTE_JS capability, so a cookie-only AWS WAF application
was rejected after a paid solve and the answer had to be bought again.
Share isEmptyCaptchaCallback() between application and permission checks so
an unused callback is treated as omitted, and make the rejection message
point at the stored answer instead of another solve.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Use documented AWS widget and invisible-challenge fallback modes, preserve structured answers, validate provider parameters before spending, and enforce required browser identity during application. Retain task-bound Hugging Face signup progress across observed CAPTCHA interruptions. Add mirrored regression coverage and update integration references.
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
An enabled CAPTCHA provider could return a token that never reached the site's completion callback, leaving the page and agent blocked. Pending provider responses, token-only answers, manual completion, and same-URL reloads could also leave the solve state stuck or permit another paid attempt.
This mirrors the recovery fixes across Chrome and Firefox:
Validation on the committed snapshot:
Reload the updated extension and refresh an existing CAPTCHA page before retrying so its callbacks can be captured. Live paid-provider acceptance on Hugging Face was not exercised.