Waitcher CLI

Synthetic monitoring from your repository. Describe monitors in waitcher.json next to your code and the end-to-end tests you already have, then plan and deploy them from your terminal, CI or coding agent. Waitcher runs them on a schedule, keeps the evidence and alerts you when something breaks.

Requires Node.js 24.15 or later.

npm install --global @waitcher/cli
waitcher --version

Quickstart

cd your-repository
waitcher auth login                       # signs in through your browser
waitcher config init --target https://example.com/
waitcher deploy plan --env production
waitcher deploy apply --env production --based-on none

New monitors start paused. Run one once with waitcher run start --id MONITOR_ID --wait, then waitcher monitor resume --id MONITOR_ID to schedule it.

To monitor an API or browser journey, point an entry in waitcher.json at an e2e test file, pin the test runtime and check the test locally before deploying:

waitcher runtime install --yes
waitcher deploy plan --env production --verify

To watch how a page looks, add a visual entry: Waitcher screenshots the page on a schedule and compares it with the capture you approved (visual checks).

{ "key": "home-look", "type": "visual", "path": "/" }

Coding agents

waitcher skill install

installs the Waitcher skill where Claude Code and other agents look for it. waitcher doctor checks the setup, waitcher explain CODE explains any issue code, and waitcher help TOPIC prints exact syntax for this version.

More

• Guide: https://waitcher.dev/docs/
• For agents: https://waitcher.dev/llms.txt
• Free accounts get 5 monitors every 30 minutes, one of them an API or browser test or a visual check every 2 hours.

Every command prints JSON. Help and --version work offline.