Analysis updated 2026-05-18
Run a self hosted service that solves common CAPTCHA types without paying an external provider.
Integrate the solve API into an automation pipeline that needs to get past Turnstile or reCAPTCHA challenges.
Harvest clearance cookies like Cloudflare's cf_clearance or Akamai's _abck for a browser session.
Explore the interactive Swagger docs to test each supported CAPTCHA type with example requests.
| waguriagentic/captcha-solver | nekocode/filetree-skill | pku-yuangroup/openai4s | |
|---|---|---|---|
| Stars | 126 | 125 | 127 |
| Language | Python | Python | Python |
| Setup difficulty | hard | easy | moderate |
| Complexity | 4/5 | 2/5 | 4/5 |
| Audience | developer | developer | researcher |
Figures from each repo's GitHub metadata at analysis time.
Requires setting up a headless Chromium environment with a virtual display and configuring several environment variables for production use.
Captcha Solver is a local HTTP service that solves CAPTCHA challenges by running them inside a real, self hosted anti detect browser rather than sending them to an outside paid provider. It runs as a sidecar next to whatever application needs a solved CAPTCHA, and it only handles the solving step, returning a token that can be reused. Creating accounts or filling in other form fields is left entirely to whatever calls it. The service supports eleven different CAPTCHA and bot detection systems, including Turnstile, reCAPTCHA in its v2, v3, and invisible forms, hCaptcha, Cloudflare's clearance cookie, AWS WAF's silent challenge, Google's BotGuard token, DataDome, PerimeterX's press and hold challenge, Akamai's Bot Manager cookie, Aliyun's slide puzzle, and Arkose's FunCaptcha visual puzzle. Each of these is handled by its own solver module, and each one launches the underlying browser engine to either automate the challenge directly or harvest the resulting token or cookie. The service exposes a small FastAPI based HTTP API with endpoints for health checks, service status, recent solve logs, and the main solve endpoint that dispatches work based on a requested type. Interactive documentation is generated automatically and available through both a Swagger UI and a ReDoc page, including example request bodies for each supported CAPTCHA type. Most endpoints require a bearer token when reached through a public domain, though the service does not enforce authentication on its own when accessed locally. In production it is meant to run as a systemd service under a virtual display so that browser based solving still works on a server with no physical screen attached. Configuration is controlled through environment variables covering the listening port, whether browsers run headless or headed, optional geo alignment of browser settings to a proxy's location, and a guard that by default blocks the service from being pointed at private or internal network addresses. The project is written in Python and built on a separate library called CloakBrowser.
A self hosted local service that solves CAPTCHA challenges like Turnstile, reCAPTCHA, and hCaptcha using a real browser engine and returns reusable tokens.
Mainly Python. The stack also includes Python, FastAPI, CloakBrowser.
The README does not state a software license for this project.
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.