APXY is a local network proxy and debugging tool that captures, inspects, mocks, replays, and diffs HTTP/HTTPS traffic. It is built for developers and AI coding agents with a CLI-first workflow and an optional Web UI.

How is APXY different from Charles Proxy or mitmproxy?

APXY is purpose-built for the modern developer workflow including AI coding agents. It provides structured output (TOON format) that AI agents can reason over, a CLI-first API for scripting and automation, and first-class support for CI/CD, Docker, and headless environments. Unlike Charles Proxy, APXY requires no GUI and unlike mitmproxy, it includes API mocking with scripting and a built-in Web UI.

Does APXY work with AI coding agents like Claude Code and Cursor?

Yes. APXY has dedicated integrations for Claude Code, Cursor, GitHub Copilot, and OpenAI Codex. It returns compact, structured network traffic so AI coding agents can reason over real HTTP requests and responses instead of screenshots or raw HAR files.

APXY has a free tier that lets you capture traffic and explore the Web UI with no account or credit card required. Paid one-time licenses (Pro at $59, Personal at $79) unlock unlimited traffic history, API diagnosis, scripting, breakpoints, network simulation, and multi-device access.

Does APXY work in CI/CD pipelines and Docker?

Yes. APXY runs headlessly and works in local development, CI pipelines, SSH sessions, Docker containers, and background scripts. The core CLI workflow stays the same across all environments.

What operating systems does APXY support?

APXY supports macOS, Linux, and Windows.

For Continue

Use APXY with Continue to debug API failures without leaving your editor

Continue brings AI coding assistance into VS Code and JetBrains. APXY gives it the live HTTP traffic your editor cannot see — turning vague API errors into inspectable, replayable evidence.

Recommended workflow

Run APXY alongside Continue so your AI assistant can reason over real captured traffic rather than reading error messages alone.

Start APXY and configure your app to route traffic through the local proxy.
Reproduce the failing API call or integration error inside your development environment.
Copy the captured request and response from APXY into your Continue chat context.
Ask Continue to diagnose the failure, then replay the fixed request in APXY to confirm the response changed.

Why APXY fits

Continue reads your codebase — APXY adds the network layer your codebase cannot describe on its own.
Structured APXY exports drop into a Continue context window without wasting tokens on noise.
The mock and replay loop means Continue can validate fixes before you redeploy.

Take the fast path

Install Free View Examples

FAQ

What is APXY for Continue?

Continue brings AI coding assistance into VS Code and JetBrains. APXY gives it the live HTTP traffic your editor cannot see — turning vague API errors into inspectable, replayable evidence.

How do you use APXY with Continue?

Start APXY and configure your app to route traffic through the local proxy. Reproduce the failing API call or integration error inside your development environment. Copy the captured request and response from APXY into your Continue chat context. Ask Continue to diagnose the failure, then replay the fixed request in APXY to confirm the response changed.

Why do developers pair APXY with Continue?

Continue reads your codebase — APXY adds the network layer your codebase cannot describe on its own. Structured APXY exports drop into a Continue context window without wasting tokens on noise. The mock and replay loop means Continue can validate fixes before you redeploy.