A single flow’s graph shows its nodes. The Flow Map zooms out one level: every
.aether file in the workspace as a card, with arrows showing which flows call which
through subflow nodes.
Open it from the activity bar (the map icon) or the command palette (View: Flow Map).
Reading the map
Flows are laid out by hierarchy: flows nothing depends on at the top, the subflows they call below them, standalone flows alongside. Each card shows:
- The flow’s name, path, and node count.
- A run badge if it has executed (passed, failed, or running), including runs it received indirectly, marked via connection, when a parent flow invoked it as a subflow.
- Red background: the file has a parse error and needs attention before it can run.
- Faded ghost card: a file referenced by some flow’s subflow node that doesn’t exist
on disk (a broken
path, or a file that was moved without updating its callers).
The arrows between cards are subflow relationships: parent → child.
Acting on it
- Click a card to open that flow in the editor.
- Press ▶ on a card to run that flow right from the map; states update as it runs.
When it earns its place
- After a refactor. Moved or renamed a flow? Ghost cards point at every caller you forgot to update.
- Suite health at a glance. Run flows and watch the map become a pass/fail dashboard.
- Understanding an inherited repo. The call structure of a workspace you didn’t write, visible in one screen.
Next: Share flows with Git for what a teammate sees of the same map, or run a flow from a card and watch the result land in execution history.