Draw the flow. Read the run.

1. Start with a document

Open the UI served by the JAR at http://127.0.0.1:8080. Load GraphML or Graphify JSON by file picker, drag and drop, or a file query parameter. Graphify JSON is view-only; GraphML is the executable and saveable workflow format.

To build a new workflow, choose New, then turn Modify on. The editor refuses graph changes while Modify is off to protect browsing from accidental edits.

2. Add catalog nodes

Choose a behavior from the node catalog on the left. The inspector shows its typed form and marks required fields with an asterisk. Standard implemented behaviors include:

• log for an intentional workflow message;
• template for payload-aware text;
• cel-transform and cel-decision for checked transformations and routing;
• http-request for an action constrained by deployment allowlists.

llm-prompt and agent remain unconfigured until an integrator supplies an adapter. program is experimental and disabled in the default distribution.

3. Connect the graph

With Modify on, drag from one node to another, or select Connect and choose the source and target. Invalid targets are described before commit. Escape cancels the gesture.

Keyboard path

1. Tab to the graph canvas and use arrow keys to move the visible node cursor.
2. Press E on the source node.
3. Move to the target with arrow keys, then press Enter.
4. Press Escape at any point to cancel.

Select an existing edge and press R to reconnect its target, or Shift+R for its source. Shift+Left/Right cycles through incident edges.

4. Test before real effects

Test (or Ctrl/⌘+Enter) traverses the graph in mode=test. Node behavior is bypassed: no HTTP action, template rendering or model invocation runs. The result lists bypassed nodes.

Run submits mode=run after warning that real effects may follow. Review every controlled action and deployment allowlist before confirming.

Loops need care: Test also bypasses timing behavior, so a delay does not pace a cycle. Current editor Pause, Stop and Force stop controls are declared but inert. Manage a live execution through the documented server routes or CLI.

5. Follow activity

The activity panel streams node transitions over Server-Sent Events. It correlates events by sequence, execution ID, graph version and node ID; the server terminal emits matching structured JSON fields.

6. Save without losing work

Use Ctrl/⌘+S to save executable GraphML. Undo and redo cover node, edge, property and movement edits. The UI warns before a new workflow, file load or page exit would discard unsaved changes.