sniper-operator

name	sniper-operator
description	Use when operating a local Sniper proxy through sniper-cli for session switching, Capture record review, Scope updates, Replay tabs, fuzzer runs, held-request control, Web Socket inspection, auto-replace updates, color tag and note annotations, or Sniper skill installation.

Sniper Operator

Use sniper-cli for all Sniper operations. Prefer --output compact JSON envelopes and avoid scraping the desktop UI.

When to use

• Inspect or switch Sniper sessions
• Read Capture HTTP or Web Socket records
• Change Scope patterns
• Open, update, or send Replay tabs
• Seed Replay or Fuzzer from Capture HTTP history
• Set Fuzzer templates and payloads, then run them
• Toggle request holding and forward or drop held requests
• List or replace auto-replace rules
• Set color tags and notes on HTTP records
• Install Sniper skills into Codex or Claude

Workflow

1. Make sure Sniper Desktop is running, or pass --api http://127.0.0.1:PORT.
2. Start with sniper-cli session list and switch deliberately before mutating anything.
3. Prefer sniper-cli call <operation> --input <json|@file|-> for automation; successful call output is wrapped in the envelope data field. Legacy subcommands keep raw JSON success output. On any failure, use error.code, error.retryable, and error.hint.
4. Prefer sniper-cli call <operation> --input <json|@file|-> for automation, using operation names from sniper-cli manifest.
5. Prefer --stdin or --request-file for large raw requests.
6. Treat Replay target override fields as the connection target only. The raw Host: header stays in the request text.
7. For any manifest operation with side_effect: "write", run --dry-run first and use --yes only after reviewing the plan.
8. Sniper preserves captured sensitive values such as cookies and authorization headers; summarize large or sensitive JSON responses instead of pasting them in full.

Common commands

sniper-cli --output compact manifest
sniper-cli --output compact schema input replay.send
sniper-cli --output compact call capture.http.list --input '{"limit":20,"page":true}'
sniper-cli --output compact call replay.send --input '{"tab_id":"<tab-id>"}' --dry-run
sniper-cli --output compact call replay.send --input '{"tab_id":"<tab-id>"}' --yes
sniper-cli --output compact session list
sniper-cli session switch --id <uuid> --dry-run
sniper-cli session switch --id <uuid> --yes
sniper-cli --output compact capture http list --limit 20
sniper-cli --output compact capture http get --id <uuid>
sniper-cli capture http replay --id <uuid> --dry-run
sniper-cli capture http replay --id <uuid> --yes
sniper-cli capture http fuzzer --id <uuid> --dry-run
sniper-cli capture http fuzzer --id <uuid> --yes
sniper-cli capture http annotate --id <uuid> --color red --note "suspicious" --dry-run
sniper-cli capture http annotate --id <uuid> --color red --note "suspicious" --yes
sniper-cli scope get-scope
sniper-cli scope set-scope --pattern '*.example.com' --dry-run
sniper-cli scope set-scope --pattern '*.example.com' --yes
sniper-cli replay list
sniper-cli replay open --transaction-id <uuid> --dry-run
sniper-cli replay open --transaction-id <uuid> --yes
sniper-cli replay send --tab-id <tab-id> --dry-run
sniper-cli replay send --tab-id <tab-id> --yes
sniper-cli fuzzer set-template --transaction-id <uuid> --dry-run
sniper-cli fuzzer set-template --transaction-id <uuid> --yes
sniper-cli fuzzer set-payloads --file payloads.txt --dry-run
sniper-cli fuzzer set-payloads --file payloads.txt --yes
sniper-cli fuzzer run --dry-run
sniper-cli fuzzer run --yes
sniper-cli capture intercept on --dry-run
sniper-cli capture intercept on --yes
sniper-cli capture intercept list
sniper-cli capture intercept forward --id <uuid> --dry-run
sniper-cli capture intercept forward --id <uuid> --yes
sniper-cli capture web-socket list --limit 20
sniper-cli capture web-socket get --id <uuid>
sniper-cli capture auto-replace list
sniper-cli capture auto-replace set --file rules.json --dry-run
sniper-cli capture auto-replace set --file rules.json --yes
sniper-cli capture oast configure --provider custom --url https://oast.example --token-stdin --dry-run
printf "%s" "$OAST_TOKEN" | sniper-cli capture oast configure --provider custom --url https://oast.example --token-stdin --yes
sniper-cli skills install --codex --dry-run
sniper-cli skills install --codex --yes

Guardrails

• If sniper-cli is missing from PATH, say so briefly instead of falling back to GUI scraping.
• Do not switch sessions silently before changing scope, Replay state, or queued-request decisions.
• Use capture http get, replay list, or capture web-socket get before making assumptions about stored request state.