Analyze traffic on the Mac
Give an agent a scoped question about captured traffic instead of sending it the entire response.
Ask for the answer, not the payload
Suppose a catalog refresh displays the wrong total. An agent could ask for every item and add the prices in its conversation. With JoesProxy, it can instead identify the captured response and ask the Mac running the proxy to add one field. The agent receives a result and information about its source, not the original item list. “Edge” here means the capture Mac, not a cloud worker or a model running on the phone.
- Connect the agent and capture a refresh in an app you control. Ask it to identify the relevant request using session summaries.
- Check toolset status before asking for more data. Look for the analysis method, accepted input and limits. An exact calculation and a heuristic finding answer different questions; neither implies permission to read the source.
- Give the agent a narrow instruction: “For this catalog response only, sum the numeric price field under items. Report whether the selection was complete. Do not return individual items.” Follow the calculation walkthrough to check its answer.
Choose the smallest useful result
| Question | Start here | What it doesn’t establish |
|---|---|---|
| Which request failed? | A session search and the matching status. | Why the app failed. |
| Was a field absent, null, or the wrong type? | Field statistics over one complete selected collection. | What the missing value should have been. |
| Did the player request the expected rendition? | Manifest structure and related sessions. | Whether playback looked or sounded right. |
| Was the compact answer cheaper to obtain? | A workflow receipt comparison. | Model tokens or cost without provider receipts. |
When the agent can’t answer
A calculation can require sensitive-read permission even when it returns only a count. Review the request on the Mac. If the retained body is missing or the selection changed, don’t let the agent interpret “unavailable” as zero or silently substitute another request. Identify a new authorized capture and try again. Aggregates can themselves be sensitive; share only the result you need.