Most work happens through the agent. Delta also has two editors you drive yourself.
Delta Editor
The code editor. It is always available and needs no setup.
It opens an entry or a template with three panels for HTML, CSS and JavaScript, and writes to the same place the agent writes to. Open it from Delta → Editor, or from the Open in Delta Editor link on a page in the posts list.
Use it for a small correction you can make faster than you can describe: a wrong class, a typo in a heading, a spacing value.
The block editor
When a page carries a Delta design, the block editor no longer edits the body. It tells you so and links to Delta Editor. The title, the publish controls, the featured image and the other boxes work as they always did.
A page with no Delta design behaves as a normal WordPress page.
UI Editor
A visual editor: chat beside a live canvas of the page. You describe a change and watch it apply.
UI Editor is a feature and it is off by default. Turn it on under Delta → Features first. Until you do, the editor and its menu do not appear. It is marked unstable, which means it works and its behaviour can change between releases.
Once it is on, open a page with the Open in Delta UI Editor link.
UI Editor needs your own API key
The chat runs on your account with OpenAI or Anthropic, so you supply a key. Set it under Delta → UI Editor. You can set both and choose which is active, and you can pin a default model.
The key is stored as a secret. It is never sent to a connected agent over MCP, and it is not returned to the browser after you save it. It is used server-side, for UI Editor chat, and nowhere else.
Which to use
| Situation | Use |
|---|---|
| Describing a change in words | Your agent |
| A quick fix in the markup | Delta Editor |
| Working visually on one page | UI Editor |