# How to understand traffic from a saved HAR or SAZ file with rea

Repo: [morluto/rea](https://github.com/morluto/rea) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README

Feed a saved network capture to your agent to see requests, responses and the payloads they expose.

**Who it is for:** Developer debugging how an app talks to its server using a capture they already recorded

**The problem:** A raw capture has hundreds of requests and no clear picture of what the app actually sends.

**The outcome:** A readable breakdown of requests, responses and exposed payloads tied to source locations.

## Steps

1. Export your traffic as a HAR file or a Fiddler Everywhere SAZ file.
2. Run npx rea-agents setup and restart your agent.
3. Ask the agent to analyze the capture with REA.
4. Ask it to explain the calls behind the feature you are tracing.

## Prompt to paste into your agent

```text
Use REA to analyze the network capture at <path to .har or .saz>, list the key requests and responses, and explain which calls drive <feature>. Verify each claim against a specific request in the capture.
```

## Caveat

Captures may contain tokens and personal data, so scrub them before sharing. On Linux, native mitmproxy captures need mitmdump installed.

Dual-use notice: only use this on software, sites and systems you own or are authorized to test.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/morluto-rea/replay-saved-network-capture/