Skip to content
HamstikHamstik Docs

CLI automation and scripting

Automation should treat the CLI and Public API as machine interfaces:

  • store PATs in a secret manager, never in a repository or command history;
  • request the smallest set of scopes and resources needed;
  • prefer JSON output for scripts;
  • treat cursors as opaque values and send them back unchanged;
  • branch on stable API error codes, not English messages; and
  • use idempotency and revision/ETag behavior for safe retries.

The executable examples will be added when the CLI’s verified command names are available. See API operations for the current pagination, idempotency, and concurrency rules.