Pax Connect for Mac · App interface is in Chinese
Mac proxy client · Built on sing-box
Pax Connect is a sing-box based Mac proxy client that routes Claude Code and Codex without environment variables, manages relay API settings, and tracks token usage and cost locally.
How to set up a proxy for Claude Code →
macOS 26 or later · Apple Silicon
App interface is in Chinese
Bring your own routes and API service
claude in the terminal needs no env vars — Pax takes over its traffic
Pick a Profile and write it to Claude Code and Codex configs
Reads local logs for tokens and API-equivalent cost
Open Connections, import your own connections, choose a target and test as needed. Addresses and measurements are simulated.
Actual Pax Demo interface · In-memory simulated data · Chinese UI · Captured November 11, 2026Open Traffic monitoring → Rules, select a package, then check match scope, destination and priority.
Actual Pax Demo interface · In-memory simulated data · Chinese UI · Captured November 11, 2026Open Traffic monitoring → Overview to compare source, target and actual route.
Actual Pax Demo interface · In-memory simulated data · Chinese UI · Captured November 11, 2026Open Model usage → Profile. Distinguish written configuration from unapplied profiles. test.example is a demonstration address.
Actual Pax Demo interface · In-memory simulated data · Chinese UI · Captured November 11, 2026Open Model usage → Overview, select dates, then compare cost, tokens and cache.
Actual Pax Demo interface · In-memory simulated data · Chinese UI · Captured November 11, 2026Open Model usage → Session analysis, then select a task in the session list.
Actual Pax Demo interface · In-memory simulated data · Chinese UI · Captured November 11, 2026Three things
Get online, point to your API service, and see what it costs, all in one Mac app. Every part is shown with the real interface.
TUN takes over system traffic, so Claude Code and Codex need no environment variables, and you can see which route they actually used.
Proxy routing and rules (Chinese page)Claude Code proxy setup
Save your own relay or custom API address and write it into the Claude Code and Codex config files, then switch whenever you need.
API profile switching (Chinese page)Claude Code relay setup (Chinese page)
Reads local logs and totals tokens and estimated cost by date, model and session, with the main session and subagents shown separately.
How it works
Three things do the work, and each one can be checked in the interface.
Traffic is taken over at the system level, and you can switch between TUN and the system proxy. Command-line programs in the terminal go through it too, with no per-program setup.
Claude Code and Codex need no HTTPS_PROXY variable, and their config files stay untouched for proxying.
Traffic monitoring shows the actual route and the matched rule per application, and recognizes connections from the claude and codex processes. Rules can only select .app applications, so command-line programs need domain rules.
Network core
The network core is sing-box. Pax adds the Mac interface, routing rules, AI configuration and usage tracking on top. You bring your own route (node or subscription); Pax does not supply one. Pax Connect is an independent client, not an official sing-box product.
Route formats
Usage
Pax reads the local Claude Code and Codex logs and totals tokens, cache and estimated cost by date and model, without adding a forwarding gateway. The point is to keep context under control: the longer the context, the more each request costs, and the faster your quota burns.
Usage monitoring (Chinese page)Check Claude Code usage
The card on the side is a concept illustration with sample numbers, not a screenshot.
Session analysis · Save cost and quota
Every request resends the whole context, so the longer it gets, the more it costs and the slower it runs. Pax marks where a session goes over the limit. Start a new session there and the same quota goes further.
Read input and cache composition. Thresholds are economic references.
The same horizontal position is the same request. Output cost is excluded.
Check model, reasoning effort and cache changes before drawing conclusions.
Every request resends the whole context. A task is often a dozen or more requests, so at 300k context it resends 15 × 300k = 4.5M tokens. For GPT models, above 272k the price per token doubles (input ×2, output ×1.5). Claude Opus and Sonnet have no surcharge, but cost still grows with context. On a subscription, quota also burns faster.
With a very long context the AI replies more slowly and is more likely to miss details from earlier on: slower and dumber. Carrying on spends more tokens for less result.
Each model has a limit line, such as GPT 272k (warning at 250k), Claude Opus 200k (warning at 150k) and Sonnet 250k. Each request is marked safe, warning or over limit, and the chart says “over limit from request N”. A cost ratio of ×2 means an over-limit request’s input costs twice the safe-zone average. Pax also shows the estimated excess cost.
Rule of thumb: once context is in the over-limit zone, start a new session.
Costs are API-equivalent estimates, not bills. Official subscription quota is not shown.
Route formats
Import node links or subscriptions you already have. These are the supported protocols and variants.
Compare
Clash and Surge are great at general proxying. But to make Claude Code and Codex run smoothly you still handle terminal proxying, API config switching and usage tracking yourself. Pax puts all three in one app.
| General tools such as Clash and Surge | Pax Connect | |
|---|---|---|
| Designed for | People who want to manage traffic for every app | Developers who code with Claude Code and Codex every day |
| Proxy for claude and codex | Set HTTPS_PROXY and similar env vars, or enable enhanced mode and write rules yourself | Turn on TUN takeover, no env vars; the traffic monitor shows which route claude and codex took |
| Switch relay / API service | Out of scope; edit settings.json and config.toml by hand | Save several Profiles and write one to Claude Code and Codex in a click |
| Tokens and cost | Out of scope; find another tool | Reads local logs for tokens and estimated cost by date, model and session |
FAQ
The generic way is the HTTPS_PROXY environment variable, or the env block of ~/.claude/settings.json. With Pax TUN takeover turned on, you need neither.
Not directly. Rules can only select .app applications, not command-line programs. A domain rule gives a similar result, and claude process traffic is still recognized in traffic monitoring.
No, and it does not recommend any relay or node provider. You bring your own routes and API service; Pax handles import, routing and writing configuration.
Pax reads local Claude Code, Codex and DeepSeek Harness logs and shows tokens, cache and estimated cost. Cost is an API-equivalent amount, not a bill, and official quotas and limits are not shown.
Start a new one once the context is in the over-limit zone. Pax’s session analysis marks safe, warning and over limit per model, for example above 272k for GPT and above 200k for Claude Opus. Past that point every request resends a very long context: it costs more, runs slower and misses details more often. Carry the key points into a new session so tokens go to useful work and the same quota does more.
It imports Base64 subscriptions and node links, but not Clash YAML or sing-box JSON.
This is an unnotarized beta for Macs with macOS 26 or later on Apple Silicon. The button downloads the installer; read the first-launch notes before opening it.
Requires a Mac with macOS 26 or later on Apple Silicon. The app interface is in Chinese only.
MADE FOR YOUR MAC
Get the Mac installer. Read the system requirements and installation notes before opening the app.
