Features
Solve CAPTCHAs from Agent mode
Agent mode can now solve reCAPTCHA v2, reCAPTCHA v3, hCaptcha, and Cloudflare Turnstile challenges without leaving the task flow. Solves are routed through an optional YesCaptcha/AntiCaptcha-compatible remote endpoint first, then fall back to a built-in active-browser local model (OWL-ViT on 2–7.99 GiB hosts, Florence-2 at 8 GiB+). Local weights are fetched on first use into persistent data/captcha-model/; nothing is bundled into the image.
Do Nothing action block
A new do_nothing action block is available in the block picker. Drop it onto the canvas as a placeholder while you're drafting a task, or use it as the body of an If or On Error branch when you want the branch to fall through without side effects.
- The block takes no configuration. It logs
Do nothingand completes successfully. noopandpassare accepted as aliases and behave identically.
API trigger endpoint now accepts bodyless requests
POST /api/tasks/:id/api no longer requires a JSON body or a Content-Type: application/json header. Requests without a parsed body are treated as {} and the task runs with its default variables. Tools that can't set request headers on outbound calls (for example, Clay's HTTP action) can now trigger a task with a bare POST to the endpoint URL.
Full endpoint URL and method in the API trigger panel
The task editor's Trigger via API panel now shows the complete origin-aware endpoint URL (for example, https://your-figranium.example.com/api/tasks/task_1/api) with a POST method badge next to it. The copy button copies the same full URL, so you can paste it straight into external tools without prefixing your instance origin by hand.