Repository navigation
v0.5.0
brainproxy 0.5.0
This release makes the project a complete record of what was sent, and of who sent it: you, the app, or an AI agent through MCP. It also adds a batch of testing features in the desktop app.
Projects are upgraded to schema v14 when this version opens them. After that, 0.4.x can't open them.
Records you can rely on
- Every request is recorded before it goes out. This covers
send, races,ws send, logins and session checks, check templates, API document fetches and OAuth discovery. A request still leaves a row if the command is stopped, killed or crashes. The app's Stop and an MCP cancel send SIGTERM first, so a stopped request is recorded as cancelled; on Windows it keeps the "sent; no response recorded" row. WebSocket runs are recorded as they happen. proxy stopand restart wait for requests in flight. Ones still unanswered are recorded as stopped.- Who did what. History rows record their origin:
gui,cliormcp(an agent). They also record the proxy client's address, the TLS server name used, and who edited a request before it went out (intercept or match-and-replace rule).- Findings record who added them, who last changed their state and their note, and when. Reports say so, e.g. "confirmed via MCP (an agent)", and list findings an agent marked false positive.
history list --origin mcpfinds an agent's traffic, and Traffic has a By column.
--no-storekeeps a row. The row has the request line without the query string, so a send is never invisible.- Rescanning keeps triage.
scan passive --rescankeeps your state and notes on findings it finds again.
What an agent can do through MCP
- Refused:
--no-storeandfuzz run --store none|matches;- a proxy listening anywhere but loopback (start, restart, and saving that as the proxy setup);
- saving a redirect or invisible mode as the proxy setup;
browser open;findings remove;- replacing a finding's write-up.
--snimust be in scope. A server name other than the target's has to be listed by name in the scope, whoever sends.- Naming a request isn't opting in.
scan active --history-idandauthz run --history-idneed--include-methodsfor DELETE, PUT, PATCH or a GraphQL mutation.authz runrefuses a named logout unless--excludeis changed. The app asks before passing these. - Check templates follow the same rules. Their requests are recorded, and their PUT, PATCH and DELETE requests or mutations need
--include-methods.
New in the app and the CLI
- Replay:
- per-tab send options: HTTP/2, send as typed, SNI, timeout, TLS checks, don't record;
- Stop;
- racing a request (last-byte sync or the single-packet attack), with each race's rows tagged;
- pasting a cURL command as a tab, and Copy as cURL;
- tabs kept in the project (
replay tabs list|save).
- Traffic:
- search inside requests and responses, and saved filters;
- scan a request, test its access control, or remove a highlight from the right-click menu.
- Findings: add findings found by hand (
findings add|remove), kept apart from scanner findings in compares and gates. - Site map: import an API definition into history without scanning it.
- Proxy:
- invisible mode, a redirect, and who can connect, kept per project (
proxy setup show|set); proxy restart, so a port move can't be cut into.
- invisible mode, a redirect, and who can connect, kept per project (
- Codec: gzip, zlib, deflate and brotli, and a smart decode that finds the layers and says why it stopped.
- Guided API scan: says when a new server sets a saved query key aside, and won't start or import without it.
Behaviour changes
- A failed HTTP/2 race records every copy and exits 3, with each copy's id in
data.results. - Every check-template request is recorded, so
--checks nucleiruns add many more history rows. - An imported API document's fetch is recorded with the response head only. The body's length and sha256 are noted instead, since the document can hold credentials.
npm run devprints a#bridge=link; the dev UI works only when opened from it.
Known limitations
Not covered yet:
- narrowing the recording scope hides proxy traffic (#82);
- the Host header isn't checked against scope, on purpose, for Host-header tests (#83);
- remaining provenance gaps (#84);
- crawl, authz, fuzz and scan attacks still record after the response (#85);
- smaller items: #86, #87, #88.
Thanks to @L1ghtn1ng for PRs #70–#81.