Plonix documentation
How to use Plonix, tool by tool: capture traffic, explore it, experiment on the Bench, prove what you find, and work with Claude. Plus how Plonix keeps your data and updates on your terms.
New to Plonix? Start with Getting started, or open the demo project from the Start screen and take the tour. The plonix command explains itself too: run plonix --help.
Get started
- Getting startedPlonix captures the traffic between your browser and the application you are testing, maps the target as you browse, and helps you experiment and prove what you find. This page…
- Install and open PlonixThe Mac app is signed and notarized by Apple, so it opens like any other app you download: macOS asks once whether you want to open it. The Windows installer is not code-signed…
- The Plonix windowPlonix is a native app on macOS and Windows. Double-click it and the Start screen opens; pick or create a project and it opens in a window of its own with capture running. Open…
- Projects, sessions and settingsA project is a folder. Plonix creates new ones in ~/Plonix/<name> unless you choose another place (on the Start screen, or plonix projects new <name> --location <dir>).
- Setting up capture on any computerPlonix aims to take you from download to captured traffic in under a minute, whatever is installed on your Mac or PC. This page covers the three things that can stand in the…
Capture and explore
- Traffic and the LensTraffic lists every request and response that passes through the project's proxy, live. The Lens shows the selected one, decoded and pretty-printed. Everything is recorded into…
- Named filters and filter packsNamed filters are shortcuts for searches you'd otherwise type over and over: "auth flows", "API docs", "hide analytics and trackers". Anyone can write them, share them as a…
- ScopeScope is the list of domains you are testing. It decides what Plonix may send to: every request from the Bench, a scan, a crawl or an agent passes one check, and a host that is…
- The MapThe Map (⌘4) lists the hosts in scope, the technologies behind them and every endpoint seen on each, with its statuses and parameters. It is how you see the shape of a target…
- RulesRules change traffic as it passes through Plonix, in plain steps. Use them to send your bug bounty handle on every request, swap a token, strip Content-Security-Policy from…
Experiment and prove
- The BenchThe Bench is where you work on one request at a time and where you run many at once. Each tab is an experiment. A tab has two panels:
- Saved users and the Access checkMost access-control bugs show up when one user can see or do what another should not. Saved users keep each user's cookies and tokens, so you can send the same request as…
- CallbacksSome problems only show when the server reaches out on its own: it fetches a URL you gave it, looks up a host name, or sends mail. Callbacks hand out a unique host for each…
- ScanningScanning in Plonix turns captured traffic and a fingerprinted application into discovered targets and reproducible findings. It is built for authorized research on applications…
- FindingsFindings (⌘7) are what you found, each with the requests that prove it attached as evidence. Plonix suggests; you decide what becomes a finding.
- ProgramsBug bounty and vulnerability disclosure programs say which assets you may test and under which rules. Plonix reads a program, shows you what it will change, and from then on…
AI and the Market
- Agents and MCPPlonix lets an AI agent work with your live project: the traffic you captured, the map of the target, detected technologies, scope and findings. It does this through MCP, the…
- The Market and skillsThe Market is where Plonix gets everything modular, in one catalog:
- Detection rulesPlonix recognises the technologies behind every host you browse (servers, frameworks, CMSs, CDNs, WAFs, identity providers, exposed admin consoles) using declarative detection…
- ExtensionsPlonix is meant to be maintained by its community. Extensions are how people add what the core deliberately leaves out: new detections, filters, tabs and panels, tweaks to how…
Your data
- UpdatesPlonix.app never installs anything on its own. Every step that changes the app on disk is the user's choice, and closing a dialog always means "no".
- Privacy and usage statisticsPlonix keeps your work on your computer. Captured traffic, projects, findings, scope and settings are stored only in folders on your disk (~/.plonix and your project folders).…
- Crash reportsIf Plonix crashes, it writes a report on your computer and sends nothing. There is no crash-reporting service: you decide whether a report goes anywhere, and you see it first.
- Code signing policyThe Windows installer, Plonix-Windows-setup.exe, is code-signed so Windows can show who published it and that it was not changed after it was built.