Wirepane: the debugging proxy Claude can read

• Why does checkout return 402 on the phone but not in the browser?
• Wait while I tap Log in, then tell me what the app sent.
• Make the feed take 3 seconds and fail one request in five.
• Answer the price socket with a mock that sends a tick on every subscription.
• Nothing shows up from the emulator. Fix it.

Claude finds the request, reads only the part it needs, compares the one that works with the one that fails, replays it with a change, writes a rule, and fixes your code. When something is in the way — a missing CA, a pinned certificate, a VPN or Charles holding the system proxy — the doctor names it and fixes it.

• list_requests

  ({ filter?, since?, limit? })

  The proxy’s state and one line per request: id, method, status, URL (long ones cut), size, time, type, WebSocket and event counts, rules, error. since lists only what is new.

• get_request

  ({ id, part?, json_path?, max_chars?, from?, limit? })

  One request, part by part: summary, headers, request, response, messages. Bodies share one budget and json_path picks one field. gRPC, protobuf, trailers, WebSocket messages and events are included.

• search_requests

  ({ text, where?, filter? })

  Which requests hold some text in their URL, headers, bodies, messages or events, with the text in context.

• wait_for_request

  ({ filter, timeout_s?, until? })

  Waits for the request you are about to trigger, and answers it the moment it ends.

• diff_requests

  ({ a, b })

  What differs between two requests: method, URL, query, headers, status, JSON field by field.

• replay_request

  ({ id, method?, url?, headers?, body?, json? })

  Sends a request again, as it was or changed, through the proxy, so it is recorded and rules apply.

• resume_request

  ({ id, action?, changes?, respond? })

  Lets go of an exchange held at a breakpoint: as it was, changed, answered by hand, or cut.

• send_ws_message

  ({ id, to, text | json | b64 })

  Injects a message into a live WebSocket, to the client or to the server.

• close_websocket

  ({ id, code?, reason? })

  Closes a live WebSocket, to test reconnects.

• add_ruleupdate_ruleremove_rulelist_rules

  The rules file, applied at once.

• track_domains

  ({ add?, remove?, set?, enabled? })

  Decrypts and records only your app’s hosts, and shows what passed through.

• export_har

  ({ filter?, file? })

  HAR 1.2 with bodies and WebSocket messages, for a teammate or Chrome DevTools.

• diagnose

  ()

  The doctor: every check, each finding with its fix.

• HTTP/2, both ways

  To clients that offer it and to servers that speak it. HTTP/1.1 for the rest, each side on its own. Plain-text h2c too, for gRPC to a local service.

• gRPC and gRPC-Web

  Trailers forwarded. Bodies are decoded without a schema: field numbers, values, nested messages. A failed call shows its status: gRPC NOT_FOUND: no such user.

• Protobuf

  application/x-protobuf bodies, decoded the same way.

• WebSockets

  Message by message, both ways, with timing and close codes. Compression is taken out of the offer, so every message stays readable.

• Server-sent events

  Event by event as they arrive, with the millisecond each one came. Made for LLM streaming APIs.

• Compressed bodies

  gzip, brotli, deflate and zstd, decoded.

• Setup → Browser

  A separate browser

  Chrome, Edge, Brave or Chromium starts with a profile of its own and trusts the proxy by SPKI hash. No certificate to install, and localhost is captured too.

• Setup → iOS

  iOS Simulator

  Use (or Boot & use) boots one, adds the CA and turns on the Mac’s system proxy, since a simulator has no proxy setting of its own.

• Setup → iOS → iPhone / iPad

  iPhone and iPad

  Listen on LAN, scan the QR code to install the profile, turn on full trust and set the Wi-Fi proxy to the address shown. The section confirms when traffic arrives.

• Setup → Android → Emulator

  Android emulator

  Start through the proxy launches an AVD behind it and opens the CA page. On a Google APIs image, Trust in all apps makes the CA a system CA until the next reboot.

• Setup → Android → Phone

  Android phone

  On USB, adb reverse points it at the proxy, so no Wi-Fi is needed. On Wi-Fi: Listen on LAN, the QR code and the proxy setting shown.

• Setup → macOS · Setup → CLI

  Mac apps and the command line

  Safari and native apps get the system proxy and the CA, one press each, and both are put back when the proxy stops. For curl, Node, Python, Go, Java and Docker it copies HTTPS_PROXY, NODE_EXTRA_CA_CERTS, SSL_CERT_FILE and REQUESTS_CA_BUNDLE.

What it repairs on its own

• Pinned hosts pass through

  A host that refuses the certificate twice is tunnelled untouched, so the app keeps working. Decrypt it again once the client trusts the CA.

• A leftover system proxy is put back

  A killed proxy can leave the Mac’s system proxy on and the Mac with no internet. A watchdog puts it back.

• Self-signed dev servers, accepted

  A dev server with a self-signed certificate gets it accepted in one press, for that host only.

• Office networks

  An upstream proxy carries every connection to the servers: HTTP, HTTPS, HTTP/2, tunnels and WebSockets. It can be an HTTP proxy that signs in with Basic or Windows NTLM credentials, SOCKS5, or a PAC file that picks per URL. The doctor offers the network’s own proxy for it.

• wirepane-debugging

  The order that works: from filter to summary to part, then search, diff, replay and verify. Also how to read gRPC, WebSocket and SSE traffic cheaply.

• wirepane-troubleshooting

  Symptom, check, fix, for everything the doctor knows, including the fix in your own app: Android network_security_config, OkHttp and iOS pinning in debug builds, Flutter HttpOverrides, and proxy settings for Node, Go, Python, Java, Docker and Unity.

• wirepane-rules

  Recipes for mocks, latency, chaos, JSON rewrites, GraphQL operations and WebSocket mocks. Every one is tested to validate.