Correct site/task, or toggle MCP exposure
All fields optional — only what’s supplied is updated. A SUPPLIED site still can’t be blanked. Setting mcp_enabled (GitHub #73 — the per-automation MCP toggle, independent of REST publish status) requires the owner role; correcting site/task does not.
承認
The dashboard's signed, HttpOnly session cookie (packages/service/src/auth.ts): base64url(payload).base64url(hmac-sha256), absolute 30-day lifetime, SameSite=Lax, Secure on any TLS deployment. Minted by POST /api/auth/signup or POST /api/auth/login (or, outside production, auto-provisioned by GET /api/session). Because it is HttpOnly, it cannot be read or attached by a browser-based API-reference "Try it" panel across origins — exercise these routes with a real logged-in browser session or a cookie-jar HTTP client.
パスパラメータ
ボディ
レスポンス
The updated automation.
The product's core object — an Automation (the engine's Flow). name is the public /v1/run/:flow endpoint and unique per org. status gates running: draft (never runnable), published (live), failing (a locator drift was detected — see needs_attention/rerecord_href).