Graph & code views

Open any .aether file and the flow editor gives you three tabs above the canvas. All three look at the same file — pick whichever fits the task.

Graph

The default view: your flow as cards connected by edges.

• Reading a node — the colored stripe on its left edge tells you the type (every node type has its own color), and the card shows a summary: method + URL for a request, the first line of code for a script, and so on.
• Reading the rings — after a run, a green ring means passed, a red ring means failed; a pulsing node is currently running. A brass ring just means it’s selected.
• Badges — ⤓ name marks a node that captures a variable; ⚠ marks a node that references a variable with no value yet (see Variables & environments).
• Select a node by clicking it — the inspector on the right fills with its details.
• Move a node by dragging. The position is stored in the file (under the node’s ui.position), so the layout travels with the flow and survives commits.
• Add nodes from the right-click menu — pick a type and it arrives prefilled with a working template. Choosing Subflow… opens a picker listing every .aether file in the workspace.
• Pan and zoom with the mouse; the controls in the bottom corner offer zoom, fit view, and a pan lock.
• Edges come from each node’s routing fields (next, then/else, body, branches) — condition branches are labeled true/false, loop bodies loop body, parallel fan-outs branch with a join edge after them. To rewire the flow, edit those fields in the node’s YAML (inspector → Node tab).

Code

The whole file in a full-featured code editor — syntax highlighting, the works. Anything you can do on the graph you can do here, plus things the graph has no gesture for (reordering nodes in the file, block comments, copy-pasting a node between flows).

If you type something the parser can’t read, a red banner appears with the error, and Run and Heal… are disabled until it’s fixed — the graph never renders a guess.

Result

The full summary of the last run — what ran, what passed, what failed — kept next to the flow it belongs to. Older runs live in the History tab of the bottom panel.

The toolbar

Above the tabs: Save (⌘S — the dot on the tab marks unsaved changes), Heal… (check the flow against your OpenAPI spec), and the brass ▶ Run button (⌘⏎ or F5).

If the file changes on disk while you have unsaved edits — a git pull, another editor — a banner offers Reload or Keep my edits. Nothing is overwritten without asking.

Working with tabs

Every open file is a tab. ⌃Tab/⌃⇧Tab or ⌘⌥→/⌘⌥← cycle through them, ⌘1–⌘9 jump by position (9 = last), and ⌘W closes the active one.