rea-captcha Portable Agent Plugin

This is the Portable Agent Plugins v1 package for rea-captcha. It gives compatible agent clients a pinned local MCP server plus a workflow skill for browser tasks interrupted by CAPTCHA or another verification gate. The package is shared by the Awesome Copilot and Hermes Agent catalog integrations; it does not create or replace a browser.

What the plugin does

• mcp.json starts rea-captcha@0.3.1 over stdio with --stateless.
• skills/rea-captcha/ teaches the agent to distinguish an action from fresh verification evidence and to keep unsupported challenges in human handoff.
• captcha_analyze classifies URL, HTML, visible text, and runtime signals already captured by the calling browser agent. It is read-only and does not connect to a browser.

The catalog package deliberately starts in stateless mode. It does not copy a browser profile, move cookies or challenge tokens, launch a solver, or assume that returning control from Bot Screen proves the challenge cleared. The five session lifecycle tools fail closed until rea-captcha is launched separately with an explicit browser configuration.

Install with GitHub Copilot CLI

After the external plugin is accepted into Awesome Copilot:

copilot plugin install rea-captcha@awesome-copilot

If that marketplace is not registered in an older or custom CLI setup, register it once first:

copilot plugin marketplace add github/awesome-copilot
copilot plugin install rea-captcha@awesome-copilot

Install with Hermes Agent

After the Hermes catalog entry is accepted:

hermes plugins install rea-captcha
hermes plugins enable rea-captcha

Start a new agent session, then ask it to inspect evidence it already has, for example:

Use rea-captcha to analyze this checkout page evidence. If it is blocked, explain what fresh evidence is required before the browser task can resume.

Same-session browser recovery

For captcha_inspect, captcha_complete, captcha_handoff, captcha_wait, and captcha_resume, configure rea-captcha against a browser session the caller already owns and launch the MCP server with --config PATH. Do not run that stateful server under the same MCP name as this stateless catalog server. The MCP tool catalog documents the lifecycle and the validation record shows the provider-test and owned-origin boundaries.

Requirements and disclosure

• Node.js 22.19+, 24.11+, or 26+ with npx on PATH.
• First start asks the user to approve downloading the exact rea-captcha@0.3.1 npm package into npm's cache; the integration does not suppress npm's prompt.
• The local server has no telemetry, hosted solver, commercial solver API, or stealth mode.
• captcha_analyze processes only evidence included in the tool call. It makes no browser or provider request.
• Provider-test actions and owned-origin image/text handling are available only in an explicitly configured stateful installation; production third-party interactive challenges remain human handoff.