Runs onWrit CloudDesktopSelf-hosted
On this page
AI navigate
The ai_navigate step asks the AI to navigate to a described destination — a section, a result, a settings page — when the path varies between runs and fixed steps would be fragile.
In a workflow, this is a step object with "type": "ai_navigate". 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 | The destination to reach, described in plain language. |
Example
A single ai_navigate step as it appears in a workflow's steps array:
{
"type": "ai_navigate",
"config": { "description": "Open the billing settings page" }
}How it behaves
- Use it to absorb minor layout changes without re-recording the whole workflow.
- Metered by tokens like other AI steps; record the path once it stabilizes.
Where it runs
The ai_navigate 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.