A simple objective
We will turn a few notes into a list of actions with a Text → Codex → Display blueprint. Set up the Codex block and its authentication first, following its documentation. To explore just the editor, start by connecting Text directly to Display.
Build the graph
- Open a project and create a blueprint named My first actions.
- Add the Text, Codex, and Display blocks from the palette on the left.
- Connect the out output of Text to the in input of Codex, then the out output of Codex to the in input of Display.
- Enter a few notes in the Text block. Select Codex and check its working directory.
Write a precise instruction
In the Codex block’s output instruction, specify the expected result and reference its input by name.
From the notes @in, produce a list of no more than five actions.
For each action, specify an objective and a concrete deliverable.
If any information is missing, flag it without inventing it.
Run the workflow and read the result
- Choose One-shot simulation, then click Execute.
- Monitor the block statuses. If a block fails, open its logs.
- Double-click Display to view the result.
- Adjust the instruction and try again. Save the blueprint through the actions menu.
What simulation actually does
Simulation is a real, one-off execution of the graph. Configured agents, API calls, and file writes can run and incur costs. The name does not mean that execution is free of side effects.
Extend your first workflow
Add a Python block to structure the data or a save block to produce a file. Change one step at a time and check the intermediate outputs: a readable blueprint depends as much on its checkpoints as on its agents.