Skip to main content
Run Dino scans on a repeating schedule. Shadow Mode monitors your API continuously, tracks health scores over time, detects schema drift, and optionally enforces breaking-change gates. Designed for long-running environments (staging servers, CI monitors, containers) and single-shot CI checks (--once).

Usage

Flags

Authentication Flags

Autonomy Levels

In enforce mode, a single breaking change terminates the watch loop. Use this in CI or pre-deploy gates where you want hard stops on API regressions.

Examples

Observe mode (default)

Runs every 5 minutes until interrupted with Ctrl+C or SIGTERM.

Enforce mode in CI

Runs a single iteration. If breaking changes are detected, exits with code 1. Perfect for CI pipelines.

Custom interval and iteration count

Runs 10 iterations, 60 seconds apart, then exits with code 0.

Long-running container monitor

Runs every 15 minutes, keeps the last 500 history entries. Handles SIGTERM gracefully for container orchestrators.
Use --once for CI pipelines and --iterations for time-boxed monitoring sessions. Omit both for indefinite monitoring.

History

Each iteration writes a history entry to .dino/history/. Entries include: Use --history-limit to control disk usage for long-running instances.

Circuit Breaker

If iterations fail consecutively, the watch loop exits to prevent runaway resource consumption.
The threshold is controlled by --max-consecutive-failures (default: 5). A single successful iteration resets the counter.

Graceful Shutdown

The watch loop handles SIGINT (Ctrl+C) and SIGTERM signals. When interrupted:
  1. The current sleep interval is cancelled immediately
  2. No new iterations start
  3. The command exits with code 0

Exit Codes