Skip to content
mycli

Running Commands

Sync your catalog

Section titled “Sync your catalog”

Your local catalog is synced automatically when you run my cli login or my library add. You can also update libraries manually:

Terminal window
my library update

This pulls the latest changes from all installed library repos. The API catalog is synced with ETag support for efficient caching and stored locally at ~/.my/cache/.

Run a synced command

Section titled “Run a synced command”
Terminal window
my cli run <slug> [-- args...]

For example:

Terminal window
my cli run deploy -- production
my cli run greet -- --name World

Arguments after -- are parsed by the command spec. Positional arguments are matched in order, and flags use --name value syntax.

Skip confirmation

Section titled “Skip confirmation”

If a command has requireConfirmation: true in its policy, use -y to skip the prompt:

Terminal window
my cli run deploy -y -- production

Run from a file

Section titled “Run from a file”

Run a spec file directly without pushing to the registry:

Terminal window
my cli run -f command.yaml -- production

This is useful for local development and testing.

Inspect a command

Section titled “Inspect a command”

View details of a cached command:

Terminal window
my cli show deploy
my cli show deploy --raw   # Output raw JSON spec

View run history

Section titled “View run history”
Terminal window
my cli history
my cli history -n 50   # Show last 50 entries

History is stored as JSONL at ~/.my/history.jsonl.

How execution works

Section titled “How execution works”

When you run a command, mycli:

  1. Loads the cached spec (or reads the file with -f)
  2. Parses positional args and flags from the command line
  3. Renders Go templates in run lines and env values
  4. Executes each step sequentially using the specified shell
  5. Records the run in history

Next steps

Section titled “Next steps”
Template Variables Use dynamic values in commands.
CLI Reference: run Full flag and option reference.