🛠️

Debug agent-built apps with APXY's local network proxy

APXY gives developers and coding agents a local proxy for capturing HTTP traffic, replaying failures, mocking APIs, and exporting network evidence without guessing from logs alone.

Jul 20, 2026
Status & Access
Current access and latest update details.
Access
Free
Updated
Jul 20, 2026, 08:28 AM

APXY is a local network debugging and API mocking proxy built for developers who now hand real debugging work to coding agents. It sits between an app and the network, captures HTTP/HTTPS requests, and exposes the evidence through a CLI plus a Web UI.

The practical angle is simple: when an agent changes frontend code, auth handling, SDK calls, or mobile flows, APXY can give it concrete request and response data instead of a vague bug report. The official docs list traffic capture, filtering, mock rules, redirects, replay/export, API diagnosis, SSL proxying, network-condition simulation, and SQL-style queries over captured requests.

Where it fits

Use APXY when a bug depends on network behavior: a backend returns a different shape than expected, a mobile client fails behind HTTPS interception, a flaky API needs to be mocked, or an AI coding agent needs exact evidence before touching code. The project also publishes workflow examples for basic debugging, API mocking, and agent-assisted troubleshooting.

The GitHub repository includes an agent skill path, examples, mock templates, docs, and install options via shell script or Homebrew. The public site lists a free tier with Web UI access, 200 traffic records, 3 active mock rules, core CLI commands, and 30-minute sessions. Paid one-time licenses unlock unlimited history and advanced controls.

Caveats before use

Treat it as a network-inspection tool, so review certificate handling, captured request storage, and team privacy expectations before using it on production traffic or customer data. The GitHub API currently reports no SPDX license for the repository, so do not assume open-source reuse rights beyond normal use of the distributed tool and published docs.

For agent workflows, start with non-sensitive local or staging traffic. Install scripts should be reviewed before execution, especially in locked-down environments. If the tool fits your workflow, the biggest value is not another dashboard; it is giving your agent a reproducible network record it can inspect, mock, replay, and use to verify its own fix.

Discussion

Sign in to join the discussion and vote on comments.

No comments yet. Start the discussion.
Keep exploring

More from this topic

More in Tools & Apps