Runs onWrit CloudDesktopSelf-hosted
On this page
Codegen
The codegen step executes a self-contained script that manipulates the page — the output of the code-generation path, saved as a replayable step. Where evaluate reads a value back, codegen acts.
In a workflow, this is a step object with "type": "codegen". 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 |
|---|---|---|
script required | string | The generated, self-contained script to execute on the page. |
Example
A single codegen step as it appears in a workflow's steps array:
{
"type": "codegen",
"config": { "script": "document.querySelector('#load-more').click()" }
}How it behaves
- The step fails cleanly if the script is empty or throws.
- Prefer recorded steps where possible — they are easier to read and repair.
Where it runs
The codegen 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.