openlogos flow show
Display the dev-flow orchestration as a read-only tree of subflows, nodes, gates and loops. By default it prints the built-in flow template; with --resolved it applies the project’s logos/flow overlay and shows the effective flow that status, next and watch actually derive from.
Synopsis
Section titled “Synopsis”openlogos flow show [--resolved] [--lifecycle <initial|launched>] [--format json]Must be run from the project root.
Options
Section titled “Options”| Option | Description |
|---|---|
--resolved | Apply the project overlay on top of the built-in flow and show the merged, effective orchestration. Without it, the raw built-in flow is shown. |
--lifecycle <initial|launched> | Choose which flow to show. Defaults to the flow inferred from the project state. |
--format json | Output a structured JSON envelope for tools such as RunLogos. |
What it does
Section titled “What it does”- Prints each subflow with its gate (
human/cmd/ none), markingentryposition andskippable - Lists every node with its
skill,for_eachandwhenattributes - In
--resolvedmode, annotates overlay operations ([add]/[modify]/[skip]/[reorder]) and marks skipped nodes - Surfaces flow warnings (for example, an overlay
@vNthat does not match the currentbuiltin_version) - The JSON envelope carries
lifecycle,resolved,overlay_applied,builtin_version,warningsand the fullflowtree
This command is purely observational: it never executes cmd: nodes, writes markers, or advances state.
Example
Section titled “Example”openlogos flow show --resolvedFlow: launched(overlay applied)
▸ implement gate: human (skippable) · code code skill: code-implementor · verify verify when: code_present