01
Live capture
Inspect requests and responses through Chrome DevTools — headers, bodies, timing, cookies and query parameters.
Chrome DevTools network intelligence
Stop staring at requests.
Start understanding them.
TraceAna captures browser network traffic, then helps you find the failure, explain the evidence, compare requests, replay calls, and move toward a fix — without pretending Chrome can do things it cannot.
No account required · local-first analysis · Chrome DevTools
TraceAna · Network capture
GET /api/products
https://api.example.com/api/products
TraceAna insight
Healthy request. 142ms response time and a successful 200 status. No immediate diagnostic signal.
The debugging loop
One request. Four useful questions.
TraceAna is organized around the questions developers ask while debugging — not around a long list of buttons.
Trace: Start with the evidence. Capture is the ground truth for everything that follows.
Explore by job
Everything you need, without the maze.
Tap a category to see only the capabilities that match the task you're doing right now.
02
Query search
Use expressions such as status:500 method:POST time:>1000 instead of digging through dropdowns.
03
Waterfall timing
Break timing into DNS, connection, TLS, TTFB and download phases where the browser exposes them.
04
Sessions & HAR
Save captures for later and work with standard HAR import/export.
05
Root Cause Analyzer
Diagnose common 401/403/404/429/5xx and CORS problems with evidence, ranked causes and confidence.
06
Performance Doctor
Score performance from observed slow calls, duplicates, polling patterns and parallelization opportunities.
07
Session Journey
Find the first meaningful failure and distinguish evidence-backed cascades from timing correlation.
08
Request Diff
Compare a working and failing request across headers, cookies and body changes.
09
Replay & Composer
Re-fire captured requests or edit method, headers and body before sending.
10
Code generation
Generate cURL, fetch, Python, PHP, Node, C# and Postman output with credentials masked by default.
11
API Contract Generator
Infer an OpenAPI 3.0 document from real traffic and label it clearly as inferred.
12
Rules engine
Block, redirect or modify supported headers, plus body-only response mocking.
13
Local analysis
Rule-based diagnosis and generated tests/docs run locally in the extension with no external AI call.
14
Agent Bridge
Optional local proxy for traffic outside the browser tab, including another app or a phone on the same Wi-Fi.
15
Tag Watch & Data Layer
Inspect GA4/GTM and other marketing tags, duplicate IDs and live dataLayer activity.
16
Privacy Scan
Detect JWTs, API keys, cookies, cards and emails before exporting captured traffic.
Why it feels different
From “show me the request” to “help me fix it.”
The point is not to replace every network tool. The point is to shorten the distance between evidence and action.
Traditional network view
→Shows data: URL, status, headers, body and timing.
→You investigate: why the call failed or slowed down.
→You reproduce: copy values into another tool.
TraceAna
✓Trace: capture the evidence.
✓Analyze: surface signals and likely causes.
✓Explain: connect evidence and compare calls.
✓Fix: replay, compose, generate and test.
See it in action
The familiar network table — with a much bigger toolbox around it.
Designed for the moment something breaks
Capture first. Select the suspicious request. Then move directly into API Intel, Performance, Journey, Composer, Rules, Tag Watch or Privacy Scan.
Get started
Install TraceAna in minutes.
Chrome is supported today. Microsoft Edge support is coming soon.
See installation guide →1
Open chrome://extensions and turn on Developer mode.
2
Choose Load unpacked and select the folder that contains manifest.json.
3
Open any page, press F12, then choose TraceAna from the DevTools tab bar.
4
Reload the page after opening DevTools. Requests will begin appearing in the capture view.
Honest limits
Powerful where Chrome allows it.
TraceAna documents platform boundaries instead of hiding them behind misleading UI.
No mid-flight breakpoints
Manifest V3 removed synchronous interception for normal extensions, so TraceAna does not pretend it can pause a request mid-flight.
Agent Bridge does not decrypt HTTPS
Inspecting encrypted traffic requires a trusted MITM certificate. The optional bridge does not provide that decryption layer.
Mocking is body-only
The supported MV3 path redirects to a data URL, so the mocked response cannot freely set a custom status or response headers.
Some headers are browser-controlled
Composer cannot freely set headers such as Cookie, Host or Origin because browser fetch rules restrict them.
Privacy by design
Your traffic is your debugging data.
TraceAna is built around local-first debugging and explicit user actions for export or optional local-agent communication.
Local analysis
Current AI-style analysis is rule-based logic inside the extension. It does not call an external AI API.
Local capture
Captured sessions are stored in your browser profile unless you explicitly export or send them using a feature you choose.
Secret awareness
The Privacy Scan can flag JWTs, API keys, cookies, card-like values and emails before export.
Optional Agent Bridge
The bridge is off by default and communicates with a local agent you run yourself, including a phone or another app on your network.
Questions
Quick answers.
For detailed troubleshooting and bug reporting, use the support center.
Where does TraceAna appear?
Inside Chrome DevTools. Open DevTools with F12, then choose the TraceAna tab. The extension is not primarily a toolbar popup.
Does TraceAna send captured traffic to an AI service?
No. The current analysis layer uses local, rule-based logic and does not make an external AI API call.
Can it debug traffic from a phone?
The optional Agent Bridge is designed for traffic outside the browser tab, including a phone on the same Wi-Fi. It does not decrypt HTTPS traffic.
Can it pause a request before it reaches the server?
No. Chrome Manifest V3 does not provide the synchronous interception needed for a normal extension to behave like a traditional breakpoint proxy.