Continuity CLI reference - Ωmegas docs

continuity <command> [options]

  scan     Read every declared configuration surface and print what was found
  report   The same scan, rendered as a multi-section report
  compat   The derived compatibility matrix, its losses, and per-item exceptions
  export   Write a redacted, content-addressed bundle you can share
  diff     Preview exactly what importing a bundle would write. Writes nothing
  import   Walk the same plan and apply only what you consent to, item by item
  enable   Turn on one quarantined item, after showing you what it is

Options

Option	Applies to	What it does
`--home <dir>`	all	Home directory to read (default: your home directory)
`--root <dir>`	all	Project root to scan for project-scope config; repeatable
`--json`	all	Emit the machine-readable result envelope on stdout
`--max-file-bytes <n>`	all	Per-file read cap; a breach is truncated and reported, never dropped
`--out <path>`	`export`	Where to write the bundle
`--payload-policy <p>`	`export`	`definition`, `definition+scripts`, or `full`
`--bundle <path>`	`diff`, `import`, `report --html`	The bundle to read
`--html <path>`	`report`	Write one self-contained HTML page rendered from `--bundle`
`--from <rt>` / `--to <rt>`	`compat`	Restrict the matrix to one direction
`--yes-inert`	`import`	Bulk-accept inert additions only

--yes-inert can never cover an authority change, an executable item, or a write that replaces content you already have. There is no blanket --yes for import.

Exit codes

Exit codes are part of the published contract; the hosted layer attaches to this CLI through exactly two things, the bundle format and these codes plus the --json envelope.

Code	Meaning
`0`	Success
`1`	Usage error
`2`	No supported runtime found
`3`	Completed with warnings
`5`	The export gate refused: a high-confidence secret reached the serializer, so nothing was written
`6`	Integrity failure
`7`	Import blocked on containment
`8`	Import aborted on drift
`9`	Import rolled back
`10`	A runtime older than this tool supports

The hosted flow’s own flags

Run with no subcommand, the CLI enters the optional hosted transfer flow. Its flags are separate on purpose:

Option	What it does
`--root <dir>`	Root to scan; repeatable; defaults to the current directory
`--output <file>`	Sensitive local preview path (default: `~/.omegas/state/previews`)
`--dry-run`	Discover and write the preview without contacting Ωmegas
`--no-open`	Print the browser link without opening it
`--yes`	Open the browser automatically; secrets still require a separate answer

The development-only --api override requires --unsafe-development-api and accepts only HTTPS or loopback origins.

⌘I