pax-connect-app
Health Warn
- License — License: NOASSERTION
- Description — Repository has a description
- Active repo — Last push 0 days ago
- Low visibility — Only 5 GitHub stars
Code Pass
- Code scan — Scanned 12 files during light audit, no dangerous patterns found
Permissions Pass
- Permissions — No dangerous permissions requested
No AI report is available for this listing yet.
The Mac proxy client for Claude Code and Codex — built on sing-box. macOS 26+, Apple Silicon.
Pax Connect
The Mac proxy client for Claude Code and Codex.
Route traffic, switch API profiles, and see token usage and cost, all in one native app.
Download ·
Website ·
Build from source ·
中文
Demo mode with simulated data. The app interface is currently Chinese only.
What it does
Pax Connect is a sing-box based proxy client for macOS, designed for developers who code with Claude Code and Codex every day. It brings three jobs into one app:
- Route through a proxy. Take over system traffic with TUN (or the system proxy), so terminal tools such as
claudeandcodexneed noHTTPS_PROXYsetup. Rules match by.appapplication, domain, or IP and send traffic to a route, direct, or block. - Manage API profiles. Save several API service addresses and apply one to Claude Code (
settings.json) and Codex (config.toml). Saving and applying are separate steps. - Track usage and cost. Read local Claude Code, Codex and DeepSeek Harness logs and total tokens, cache and estimated cost by date, model and session. Cost is an API-equivalent estimate, not a bill.
Pax Connect is an independent client, not an official sing-box product. It ships no proxy servers or routes: you bring your own (node links or subscriptions) and your own API service.
Screenshots
![]() Connections Import node links or subscriptions, pick the current route, test latency and speed. |
![]() Routing rules Rule packages; priority rules by application, domain or IP; destination proxy, direct or block. |
![]() Traffic monitoring Per-application actual route, matched rule, connections and transfer. |
![]() API profiles Claude Code and Codex cards show which profile is written to each client. |
![]() AI usage Estimated cost, tokens, requests, cache and client distribution. |
![]() Session analysis Parent session and subagents shown separately, with a per-request trend. |
Features
Network
- TUN takeover or system proxy; switch routes without dropping TUN.
- Rules by
.appapplication, domain, or IP, with destination proxy, direct, or block. Built-in packages for private networks, Google, and China domains and IPs. - An optional ad-blocking rule package (domain based, off by default).
- Traffic and connection logs: actual route and matched rule per application.
- If another VPN/TUN tool holds the network, Pax detects it and asks you to turn it off. It never stops other tools for you.
Routes
Importing supports share links and Base64 subscriptions for these protocols (see daemon/internal/importers):
VLESS (incl. Reality, Vision flow, ws, httpupgrade) · VMess · Trojan · Hysteria2 (salamander obfuscation) · AnyTLS · Shadowsocks
Not importable: Clash YAML, sing-box JSON, VLESS over XHTTP. Unsupported options in a link are rejected rather than silently dropped.
AI tools
- Local usage for Claude Code, Codex and DeepSeek Harness, read from their local logs (
~/.claude,~/.codex,~/.dsh). - Session analysis with parent and subagent breakdown.
- Profiles applied to Claude Code
settings.jsonand Codexconfig.toml.
MCP access
Open Settings → MCP in Pax to check readiness and connect Codex, Claude Code or DeepSeek Harness. New connections default to read-only; query and diagnostic access is optional. Existing permissions are preserved and conflicting entries are not overwritten. Restart or reconnect the AI client after an app upgrade.
Pax must be running for business tools. MCP does not launch the app or enable the proxy. Data returned to your AI client, including logs, domains and sessions, may be sent to that client's AI service. Entry verification checks initialization and tool discovery; it does not prove a client is connected.
Install
Requirements: a Mac with Apple Silicon, running macOS 26 or later. Intel Macs are not supported.
- Download the DMG from the latest release.
- Open it and drag
PaxConnect.appto Applications. Eject the DMG and open Pax Connect from Applications. - This beta is not notarized (no Apple Developer ID). macOS may block the first launch. Open System Settings → Privacy & Security, find the notice for Pax Connect, click Open Anyway, and confirm. Do not disable Gatekeeper.
- Import your own routes, then turn the proxy on.
Things worth knowing:
- The first time you turn the proxy on, Pax asks for your administrator password once. It is entered in a secure input box inside Pax and used to start the network core (
pax-core) as root. Pax does not changesudoersand does not cache the password. Cancelling leaves the proxy off. This is separate from the Gatekeeper prompt above. - Turn off other VPN / TUN apps before enabling Pax's TUN mode.
- Closing the window does not quit the app. Press ⌘Q to quit Pax and its background processes; turning the proxy off releases the network Pax took over.
- The interface is Chinese only for now.
- Your data (routes, subscriptions, API profiles, local records) lives in
~/Library/Application Support/Pax Connect/. It can contain credentials; do not share it. Error logs are in~/Library/Logs/Pax Connect/. Updating or deleting the app does not remove this folder; downgrading is not supported.
Privacy
- No telemetry or analytics in the app.
- AI usage is read locally from CLI logs. It does not pass through any Pax gateway. Your AI requests go from your tools to your provider as before.
- The app only uses the network for: subscription refreshes, rule updates and website icons you trigger; route tests and diagnostics (test destinations, IP info, DNS, STUN); and the model catalog from the API address you saved.
- Credentials are stored in private local files (mode 0600). That is file permission, not an encrypted vault.
More detail: paxconnect.top/privacy.
How it works
flowchart LR
App["Pax Connect.app<br/>(AppKit UI, current user)"]
D["pax-connectd<br/>(user daemon)<br/>catalog · subscriptions · stats"]
C["pax-core<br/>(root, on demand)<br/>embedded patched sing-box 1.14.3<br/>TUN · system proxy · DNS · routing"]
App <-- "gRPC over Unix socket" --> D
D -- "manages" --> C
- The app launches
pax-connectdas a child process under your user account. It handles the route catalog, subscriptions, speed tests, config generation and statistics. pax-coreruns as root only when the proxy is first turned on. It embeds a patched sing-box 1.14.3 and owns TUN, the system proxy, DNS and routing. It exits with the app.- The app never talks to sing-box directly; the only app IPC is the gRPC API in
api/.
Details: docs/architecture/runtime.md, docs/architecture/singbox.md.
Build from source
Prerequisites
- Apple Silicon Mac, macOS 26
- Xcode 26+ (Swift 6 toolchain)
- Go 1.26.x (see
daemon/go.mod) - Python 3 and
patch(used by the build to prepare sing-box) protocand its plugins, only if you regenerate protobuf code: seescripts/gen-proto.sh. Generated Go code is checked in.
Build
make daemon # pax-connectd + pax-core (arm64) -> build/
make app # builds the daemon, then the AppKit app
scripts/package-release.sh 0.1.0 # Release app + DMG -> build/releases/
make appoutput:build/DerivedData/Build/Products/Debug/PaxConnect.app.scripts/package-release.sh <version>signs ad hoc (no Developer ID, no notarization) and writes tobuild/releases/PaxConnect-<version>-<build>-arm64/. Creating the DMG needs a graphical login session and Finder automation permission.- Go builds go through
scripts/go.sh. It downloads the pinned sing-box and sing-tun sources and applies the patches inpatches/(checksum-verified) into the git-ignored.tools/directory. GOPROXYdefaults tohttps://goproxy.cn,direct; override it if you prefer:GOPROXY=https://proxy.golang.org,direct make daemon.
Repository layout
| Path | Contents |
|---|---|
api/ |
Protobuf definitions for app ⇄ daemon and daemon ⇄ core |
daemon/ |
Go: pax-connectd and pax-core |
macos/ |
AppKit app, Xcode project, Swift packages (UI, features, gRPC client) |
patches/ |
Patches and guards applied to sing-box and sing-tun |
rulesets/ |
Bundled rule sets (.srs) and their manifest |
scripts/ |
Build, packaging and code generation scripts |
third_party/ |
Third-party license texts |
docs/ |
Architecture notes and images |
License
Source-available: the core is open source (GPL-3.0); the app UI is source-available and free for noncommercial use only (PolyForm Noncommercial 1.0.0).
- App UI (
macos/): PolyForm Noncommercial 1.0.0. Commercial use needs a separate license from the copyright holder; ask in GitHub issues. - API definitions (
api/): MIT. - Everything else (
daemon/,patches/,scripts/,rulesets/,docs/): GPL-3.0 (full text). The daemon and core link sing-box, which is GPL-3.0-or-later. The patched sing-box and sing-tun changes are inpatches/.
See LICENSE for the overview. Other components keep their own licenses: see THIRD_PARTY_NOTICES.md. The name and icon are covered by TRADEMARKS.md.
Third-party marks. Pax Connect is not affiliated with or endorsed by Anthropic, OpenAI or DeepSeek. Claude, Claude Code, Codex, OpenAI, DeepSeek and other names and icons belong to their respective owners and are used only to identify the tools Pax works with.
Credits. sing-box and the SagerNet projects, the gRPC Swift and SwiftNIO teams, v2fly domain-list-community, MaxMind GeoLite2, 217heidai/adblockfilters, Simple Icons, Lobe Icons and Lucide.
Copyright (C) 2026 Moore-developers.
Reviews (0)
Sign in to leave a review.
Leave a reviewNo results found





