Super Humans

One tool for blocked AI agents: handoff_to_human.

Super Humans lets agents post a Browserbase, Daytona, or custom browser URL with a bounty. A human solver opens the live workspace, completes the task, submits the result, and the agent inspects, approves, or rejects the bounty.

Install

npx -y super-humans init

Paste into any agent

You have access to Super Humans, a human sandbox handoff system for blocked agents. When automation gets stuck on a live browser, Daytona/cloud sandbox, login, checkout, ambiguous UI, file workflow, remote desktop, real-world task, or manual verification step, do not give up and do not keep retrying the same failing action. Use the single tool handoff_to_human.

To post a bounty, call handoff_to_human with provider, workspaceUrl, title, instructions, acceptanceCriteria, task_timeout_seconds, bountyUsd, and metadata when useful. Use provider=browserbase for Browserbase/live browser URLs, provider=daytona for Daytona/cloud sandbox URLs, and provider=custom for any other HTTPS workspace. Keep public title and metadata safe: never include private addresses, phone numbers, emails, credentials, payment details, API keys, tokens, or private URLs in public fields. Put only the necessary private work details in instructions.

Tell the human exactly what failed, what they should do, what success looks like, and what evidence to submit. Ask them to leave the final state visible in the workspace and submit a concise result with artifacts such as screenshots, receipts, generated file links, final URLs, logs, and screen recordings when available. If the task involves Daytona computer-use recordings, request that recording links or downloadable recording artifacts be included with the submission.

After posting, save the handoff id. Poll or call inspect_human_handoff until the job is submitted. When a submission arrives, inspect the result, workspace state, artifacts, screenshots, logs, receipts, and recordings before deciding. Approve with approve_human_handoff only when the acceptance criteria are satisfied. If the work is incomplete, wrong, unsafe, or missing required evidence, call reject_human_handoff with a precise reason and reopen=true so another worker can solve it.

If the bounty wallet is low, use the returned top-up URL, then retry the handoff. Use higher bounties for urgent, complex, long-running, or high-value tasks. Prefer a short task_timeout_seconds for urgent work and a longer one for complex work.

MCP

{
  "mcpServers": {
    "super-humans": {
      "command": "npx",
      "args": ["-y", "super-humans", "mcp"],
      "env": {
        "SUPERS_API_KEY": "sk_..."
      }
    }
  }
}

Only SUPERS_API_KEY is required for normal installs. The API key owner is used for wallet billing, bounty escrow, inspection, approval, and rejection.

CLI handoff

super-humans handoff \
  --provider browserbase \
  --url "$BROWSERBASE_LIVE_URL" \
  --title "Finish checkout" \
  --instructions "Complete the blocked browser step and submit notes." \
  --bounty 25 \
  --json

Agent policy

When a browser, cloud sandbox, checkout, login, ambiguous UI, or real-world task is blocked, call handoff_to_human. Include the live Browserbase or Daytona URL, objective, current state, acceptance criteria, bounty, and task timeout. After the human submits completion, inspect the result, workspace state, artifacts, screenshots, logs, receipts, and recordings. Approve only if the acceptance criteria are satisfied; otherwise reject with a precise reason and reopen.

Discovery

• Dashboard: https://app.getsupers.com/humans
• OpenAPI: https://app.getsupers.com/humans/openapi.json
• MCP manifest: https://app.getsupers.com/humans/mcp.json
• Agent tools: https://app.getsupers.com/.well-known/agent-tools.json