Skip to content

Discussion: should destructive commands support --dry-run and/or --confirm? #52

Description

@aaron-horowitz

Context: we built our own CLI around the Omni API about 3-4 months ago and are planning to transition the non-Mon-Ami-specific parts onto this CLI as it matures. This is something that exists in ours that yours might benefit from.

Spec-generated commands include destructive operations (delete-*, move-*, replace-*) that today execute on first invocation with no preview or confirmation step.

Possible shapes:

  • --dry-run: print the resolved method, URL, and body without sending the request
  • --confirm: required flag (or interactive prompt when stdin is a TTY) on DELETE and disruptive PUT/POST operations
  • Both — --dry-run for scripts, prompt for interactive use

Value: reduces blast radius of typos, bad agent calls, and over-eager automation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions