Skip to content

CLI Known Issues

Mel edited this page Nov 10, 2026 · 1 revision

Each item below was reproduced with this version of the CLI. This wiki records them; it does not change the behaviour.

  • init --dry-run writes files when --components is not given. The help page lists --dry-run for init, but the plain init path does not pass it on, so stack.toml, .gitignore and AGENTS.md are created. Use --dry-run only with init --components, which honours it.
  • show <asset> --file <name>.svg refuses SVG files with binary file ... use --json for base64, because the CLI treats SVG as an image. Use --json and decode the base64 field, or read the file at stack path <id>.
  • A conflicting update moves the record. The file keeps its markers and a later update does not repeat the CONFLICT line. Check stack status after every update.
  • remote sync repeats the failure. A failed library is printed once as failed ... on stdout, and the error is printed again on stderr when the command exits 1.
  • --full and --manifest only affect the human layout. Plain output is never cut, and plain show always includes the manifest.

See also: CLI Errors and Hints, CLI Importing, CLI Output Modes.

Clone this wiki locally