Runs onWrit CloudDesktopSelf-hosted
On this page
AI continue
The ai_continue step hands control to the AI to choose and perform the next actions toward a stated goal — useful for recovery when a page changed and a recorded step no longer matches.
In a workflow, this is a step object with "type": "ai_continue". Steps run in order, and each step can read the outputs of the steps before it. See the full workflows reference for the 30+ step types.
Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.
Fields
| Field | Type | Description |
|---|---|---|
description required | string | What the AI should accomplish before returning control. |
Example
A single ai_continue step as it appears in a workflow's steps array:
{
"type": "ai_continue",
"config": { "description": "Reach the order confirmation page" }
}How it behaves
- A recorded recipe replays deterministically and only pays for AI where an ai_* step runs.
- State the goal narrowly so the AI hands control back as soon as it is reached.
Where it runs
The ai_continue step executes wherever the run executes. On your local or BYO agent there is no compute charge and the agent can reach intranet-only systems; on Writ cloud the run is metered by running time (~$0.12 per browser-hour, from your plan’s included usage wallet.
What next
- Workflows - the full step vocabulary and the workflow object.
- Recorder - capture steps by clicking through a site.
- Managed endpoints - turn the workflow into a REST endpoint, or an MCP tool.