Skip to content
sm1eePublic

Repository files navigation

Sniper — open-source web proxy for macOS and Windows

Open-source intercepting proxy for web security testing on macOS, Windows and Linux
One Rust binary with the UI built in.

Release Rust macOS Windows Debian 13 MIT License

Sniper's HTTP history with synthetic example.com traffic: a tagged POST /v1/cart request and its request and response

The Map tool on the same traffic: the browser and curl clients, the shop's origins with the servers, frameworks and sign-in each one shows, and www.example.com's endpoints in the inspector

How Sniper fits together: browser traffic, an operator and an AI agent each reach the same Sniper core — through the MITM proxy, the desktop app and sniper-cli — and the core writes captured sessions to disk


What is Sniper?

Sniper captures, holds, edits and replays the HTTP and HTTPS traffic between a browser and the sites you test. It runs on macOS, Windows and Linux (Debian 13) as one Rust binary with the UI built in. sniper-cli runs the same operations as JSON, so scripts and coding agents such as Claude Code and Codex can use it too.

Install

macOS

Install with Homebrew, which also puts sniper-cli on your PATH:

brew install --cask sm1ee/tap/sniper

Or download the latest .dmg from Releases and drag Sniper to Applications. Releases are ad-hoc signed, not notarized, so the first launch may need Open Anyway under System Settings ▸ Privacy & Security.

Windows

Download the latest -setup.exe from Releases and run it, or extract the portable .zip and open sniper-desktop.exe (Windows x64). Releases are not code-signed, so check each file against the .sha256 beside it with Get-FileHash first. Windows setup covers WebView2 and runtime prerequisites, HTTPS certificates and building from source.

Linux

Debian 13 (trixie) on x86_64 with X11 is supported from v0.3.1. Download the .deb or the portable .tar.gz from the latest release and check it against its .sha256. Ubuntu, other distributions and Debian versions, ARM, native Wayland and XWayland are not supported. Linux installation lists the GTK 3 and WebKitGTK 4.1 requirements and how to build from source.

Build from source

cargo run --bin sniper-desktop   # Desktop app
cargo run --bin sniper           # Headless proxy + UI server
cargo run --bin sniper-cli       # CLI
cargo test                       # Tests
node --test tests/*.test.cjs      # Fixture-only frontend regressions (Node.js 18+)
./packaging/macos/release-macos.sh   # macOS .app + .dmg

Quick start

  1. Download and open Sniper.
  2. Click Open browser in the top bar. That browser already sends its traffic through Sniper and trusts Sniper's certificate (which browsers). To use your own browser, set its HTTP proxy (not SOCKS) to 127.0.0.1:8080 and visit https://sniper to download and trust the root CA.
  3. Browse. Requests appear in HTTP history.

Defaults: the proxy on 127.0.0.1:8080, the headless server's UI on 127.0.0.1:23001.

Features

Category What you get
Proxy HTTP forwarding, HTTPS MITM, upstream HTTP/SOCKS5 proxy chain with login, persistent root CA, https://sniper certificate page
Browsers One click opens a browser wired to the proxy and CA, which an AI agent can also drive
Capture HTTP history, WebSocket sessions, intercept queue, match & replace rules, HTML and image responses rendered in a sandbox
TCP A loopback relay to one target for non-HTTP protocols: each connection's bytes as a two-way conversation in Hex or Text, and Intercept to hold, edit, forward or drop them. Set it up in Capture ▸ Settings; it connects directly, without the proxy chain
Findings Passive checks for sensitive data, CORS, missing headers, JWT issues, and the management endpoints and backend addresses the Service Map names. One entry per issue per host, endpoint or value; Rescan re-checks captured traffic
Scan ▸ Recon Endpoint discovery per session from a scoped crawler, urlscan and Wayback, with consent per external service and optional limits
Scan ▸ Active Scan Nuclei community templates: turned-on templates check captured in-scope traffic without sending anything; a manual scan sends the ones you pick to targets you name
Known vulnerabilities Advisories for detected front-end library versions, from retire.js, CISA KEV and FIRST EPSS files fetched once a day and matched locally: Info findings and Service Map badges, leads to confirm
Replay Edit and resend any captured request, override host and port, render the response. Fields reads Protobuf (without a schema), MessagePack, CBOR and gRPC bodies and edits Protobuf, MessagePack and CBOR request fields; binary bodies stay Base64 in every editor so their bytes never change
Fuzzer Payload lists sent at marked positions (Sniper or Battering ram), in the background with progress, Stop, a delay between requests and a stop on matching responses
Tools Decode, encode, hash, JWT inspector, data transformations
Sessions Separate workspaces, each with its own records, scope and state
Scope Host and wildcard filters beside the captured hosts and paths
Map A passive Service Map of captured origins, how they relate, and the APIs they serve
Themes 12 themes: 7 dark, 5 light
CLI sniper-cli, JSON-first automation for scripts
AI Skills Claude Code and Codex skills built on sniper-cli

Screenshots

All captured from Sniper v0.3.4 with synthetic example.com traffic.

Session

Each session's size, requests, findings, scope, pins, rules and scans, before you open it.

The Session screen: three sessions with their size, requests and findings, and the selected session's scope, busiest hosts, pinned Replay tab, Replace rules, manual scan and findings

Replay

Edit a captured request, send it again and read the answer beside it.

Replay with a pinned tab named Cart total check: a POST /v1/cart request on the left and its 201 JSON response on the right

Scan ▸ Active Scan

Run Nuclei templates against targets you name; a match opens with the exchange that proved it.

Scan, Active Scan: 14,103 Nuclei templates imported, a finished manual scan of admin.example.com with two matches, and the matched /env request and response

Intercept

Hold a request on its way out, edit it, then forward or drop it.

Intercept holding a POST /v1/cart request in the request queue, with its headers and JSON body open for editing and Drop and Forward buttons

Fuzzer

Send payload lists at marked positions and compare status, length and timing. The Fuzzer quick start (한국어) shows what to paste, how to mark a value and how to preview before sending.

The Fuzzer with a marked page parameter and its results sorted by status: quote payloads answered 500, others 400

Findings

Passive checks and template matches, each with its evidence highlighted.

Findings from passive checks and template matches, with a Spring Boot health endpoint selected and the matched words highlighted in its response

Map ▸ Flow

One origin's requests in time order, page load by page load.

Map, Flow: the client, www.example.com, api.example.com and auth.example.org as lanes, with each page load's requests and redirects drawn in time order

Tools

A pasted JWT opens the JWT tool: header and claims decoded, alg: none variants ready.

Tools with a JWT pasted in: the JWT tool opened by itself, with the decoded header and claims and alg none variants

CLI and AI agents

sniper-cli runs every operation as JSON against the running Sniper. Writes need --dry-run to preview or --yes to apply.

sniper-cli --output compact capture http list --limit 10
sniper-cli capture http replay --id <id> --dry-run
sniper-cli skills install --all --yes

The last command installs the sniper-operator skill for Claude Code and Codex. Using sniper-cli covers PATH setup, the manifest and every CLI contract.

Documentation

Guide Covers
Debugging HTTP with Sniper Starting Sniper, wired browsers, the UI from another machine, proxy chains, Render, scope and Replay
Using sniper-cli PATH setup, everyday commands, reads and writes, agent skills, CLI contracts
Service Map The passive map of captured origins, their clients and the APIs they serve
Recon Endpoint discovery, consent for external services, limits
Nuclei templates Passive templates, manual and auto scans, what never runs
Known vulnerabilities The data files, when Sniper fetches them, how versions match, the findings
Sniper in an agent harness Which part of a harness Sniper is, and what goes in and out
Using Sniper from Claude Code Installing the skill, checking that it works, what to ask for
Using Sniper from Codex The same, for Codex
Decoded value preview Reading an encoded token without leaving the editor
Architecture Why it is built this way, the tech stack, and where each part lives
Contributing Build, test, and the invariants to not break

License

MIT