NAVIGATION
WORKFLOW

One job, many agents,
one dependency graph.

When a job outgrows a single context, Elowen stops stretching the prompt and splits the work instead. Every node in the graph is a fresh sub-agent: its own clean context, its own instruction, and access that can only ever narrow from the agent that spawned it.

The graph decides what may start when. Nodes that do not depend on one another run at the same time, and a node that does is handed what its dependencies found — so no step re-derives work that is already done.

Elowen CLI workflow view: a dependency graph of sub-agents, with finished, running and pending nodes, the tool each one is on, its token spend and its elapsed time
24 NODES · 9 DONE · 6 RUNNING · 77.6M TOKENS · 13m 16s
ParallelIndependent nodes start together. Order is imposed where you declared a dependency, and nowhere else.CONCURRENT
DependenciesA node receives the results of everything it depends on as context, so a later step builds on an earlier one instead of being briefed twice.EDGES CARRY RESULTS
ObservableEvery node carries its state, the tool it is on, what it has spent and how long it has taken. Step into one and read its transcript without stopping the run.LIVE
ResumableFinished nodes stay finished. Resuming retries only what failed or never started, and their results still feed the steps below them.NO FULL RERUN
Agents and providers →