Skip to main content

Using the CLI

The terminal door: full power, scriptable to the last flag, and the door every other surface is built on. (Flag-level detail: CLI Reference.)

Watch the tour — every command family in plain words, with voiceover (~1 min):

Everyday commands​

vyasa init <workflow> --name <project>   # birth a governed project
vyasa node create --type <type> --id <id> # declare one piece of work
vyasa session start --skill <s> --mode <m> --stage <s> \
  --target <node> --intent <i> --flow simple|scoring \
  --work-style <w> --objective '<why>'   # open a sitting (8 details)
vyasa session end <id>                   # close it (archives + report)
vyasa review diff <id>                   # inspect the proposal
vyasa apply approve --id <id> --yes      # promote files (status held)
vyasa gate run --node <n>                # rehearse the checks
vyasa gate approve --node <n>            # advance (or reject/obsolete)
vyasa tree                               # the board as text
vyasa serve                              # open the console beside you

Learn the habits, not the manual​

  • Read the panels. Every command prints exact next steps — follow them literally.
  • Let refusals teach. Missing details, unready dependencies, live locks — each error names its fix. Full catalog: When It Says No.
  • Prefer --interactive while learning: guided prompts instead of eight flags; scripts keep flags (fail fast in CI).
  • Status lives behind gates only. node show tells you where anything stands and why.

Going further​

Workers: assistant list/use/add · Evidence: violations, score, state log · Health: doctor · Sharing: sync, clone — all in the CLI Reference.