meticulous-cli
Meticulous CLI
The meticulous CLI records user sessions and replays them to catch visual regressions. It is installed as part of @alwaysmeticulous/cli.
Invocation
npx @alwaysmeticulous/cli <command> [options]
The CLI can also be invoked as meticulous if installed globally or available on PATH, but npx @alwaysmeticulous/cli is the typical usage.
Command Groups
| Command | Purpose |
|---|---|
auth |
Authenticate with Meticulous (whoami, logout) |
debug |
Set up AI-ready debug workspaces for investigating replay diffs and replays |
download |
Download sessions, replays, and test runs locally |
local |
Find sessions relevant to the current branch's code changes |
project |
Inspect the project linked to an API token |
simulate / replay |
Replay a recorded session against a URL |
schema |
Output the CLI command schema as JSON (for agent/programmatic use) |
See the skill for each group for full option details:
- auth/SKILL.md
- debug/SKILL.md
- download/SKILL.md
- local/SKILL.md
- project/SKILL.md
- simulate/SKILL.md
- schema/SKILL.md
Global Options
These options are accepted by every command:
| Option | Type | Default | Description |
|---|---|---|---|
--logLevel |
string | info |
Log verbosity: trace, debug, info, warn, error, silent |
--dataDir |
string | ~/.meticulous |
Directory where sessions, replays, and other data are stored |
--rawJson |
string | — | Pass all options as a JSON string (useful for programmatic/agent invocation) |
--dryRun |
boolean | false |
Print what the command would do without making any changes |
API Token
Most commands require an API token, passed via --apiToken or the METICULOUS_API_TOKEN environment variable. The token is scoped to a specific organization/project.
Example
# Print schema for all commands (agent use)
meticulous schema
# Run a single replay locally
meticulous simulate --sessionId=<id> --appUrl=http://localhost:3000
More from alwaysmeticulous/skills
test-with-meticulous
Run after implementing any frontend change to verify its visual impact. Triggers a Meticulous test run, then inspects screenshot diffs to classify each visual change as intended or unintended. Use this before marking a frontend task as complete.
21meticulous-simulate-and-diff
Run a Meticulous session simulation against a live URL and analyze the visual output — either by inspecting screenshots directly (quick-check mode) or by comparing pixel and HTML diffs against a base replay. Use when checking whether a code change has introduced visual regressions for a specific session.
20meticulous-cli-schema
Meticulous CLI schema command for outputting the full CLI command structure as JSON. Use when you need to programmatically inspect available commands and their options, or when building tooling that drives the Meticulous CLI.
19meticulous-cli-download
Meticulous CLI download commands for fetching recorded sessions, replays, and test runs to the local data directory. Covers `meticulous download session`, `meticulous download replay`, and `meticulous download test-run`.
19meticulous-cli-auth
Meticulous CLI authentication commands. Use when logging in, checking who is authenticated, or logging out of the Meticulous CLI. Covers `meticulous auth whoami` and `meticulous auth logout`.
19meticulous-cli-project
Meticulous CLI project commands for inspecting the project configuration linked to an API token. Covers `meticulous project show`.
19