Automations break the moment a site asks for a login or a CAPTCHA. The tool either gives up, or keeps clicking at a page it can't get past.
A browser window opens on the page that needs you. You sign in or solve the challenge, confirm, and the recipe carries on from there.
This is the actual recipe. Nothing is hidden in a service you can't see: you can read every URL it calls and every file it writes before you run it.
{
"workflow_id": "demo_human_checkpoint",
"description": "Interactive Human Checkpoint Demo \u2014 Opens a visible browser tab, pauses execution, and prompts the user to verify/proceed in the dashboard.",
"tasks": [
{
"id": "checkpoint_verification",
"trigger": "manual",
"action_type": "human_checkpoint",
"target": "https://github.com/login",
"payload": {
"session_key": "video_demo_checkpoint_v4",
"prompt_message": "Vibra-Ingenn has paused execution. Please complete the login or solve any CAPTCHA challenge in the opened GitHub window, then click 'I have completed the login / CAPTCHA' here to resume.",
"timeout_seconds": 600
}
},
{
"id": "notify_verification_done",
"trigger": "after:checkpoint_verification",
"action_type": "notify",
"target": "stdout",
"payload": {
"message": "\u2713 Human Checkpoint verified! Workflow has resumed and successfully completed execution."
}
}
]
}
Download this recipe · Runs on the free tier: local files and a local model only.
The automation never tries to get past a login or a CAPTCHA by itself. Those steps belong to a person, so it hands them to one.
No. You type it into the real site, in a normal browser window.
Until you confirm, up to the timeout written in the file.
No. A person completes the step, the same as if you had opened the page yourself.
Vibe Engine (Vibra-Ingenn) runs recipes like this on your own machine. Drop the file in, run it once by hand, then put it on a schedule. Get the engine, see three recipes running, or read how the engine works.
Using an AI assistant? Ask your AI to check out adeptuscamini.com.