ProxAI Gateway

ProxAI Gateway is an on-device service that captures your coding-agent activity and ships it to ProxAI. It reads Claude Code, Cursor, and Codex session files directly from disk — no proxy, no traffic interception — and redacts API keys and other secrets on your machine before anything is uploaded.

Install

ProxAI Gateway is a single self-contained binary — you don't need Bun, Node, or any other runtime to run it.

macOS / Linux

curl -fsSL https://github.com/proxai/proxai_gateway/raw/main/install.sh | bash

Windows (PowerShell)

irm https://github.com/proxai/proxai_gateway/raw/main/install.ps1 | iex

npm — any platform, requires Node 18+

npm install -g @proxai/gateway

The binary installs to a user-writable location — no sudo and no admin prompt.

Set up

proxai-gateway setup

setup asks for your ingestion key (from the ProxAI dashboard), verifies it, writes ~/.proxai/proxai-gateway/config.toml, registers the gateway as a background service that launches on login, and starts the daemon. If the machine is already configured, setup reconciles the daemon state — starting it if it isn't running, leaving it alone if you previously paused it.

You can also pass the key inline: proxai-gateway setup <ingestion-key>.

Check status

proxai-gateway status

Shows whether the gateway is active, how much data has been captured and uploaded in the last 12 months, recent upload activity, and any active issues. Refreshes live; press q to quit.

View logs

proxai-gateway logs

Shows the most recent uploaded records — timestamp, source agent, and a snippet of what was captured. Refreshes live; press q to quit.

Use --error to list only records that failed or are in a warning state, with a description of what went wrong. Use --pending to see records queued but not yet uploaded. Use --static for a one-shot view without live refresh.

Diagnose problems

proxai-gateway doctor

Checks for common failure scenarios — daemon not running, authentication errors, network issues, upload backlog, disk space, stale binary, and more. Each finding is labelled CONFIRMED or LIKELY with a specific cause and suggested action. The output is plain text you can paste to the team if you need help.

Manage the service

proxai-gateway stop        # stop the daemon process for this session; the service stays registered and respawns on next reboot
proxai-gateway start       # start (or resume after stop) the daemon
proxai-gateway restart     # stop, then start
proxai-gateway update      # fetch and install the latest release (alias: upgrade)
proxai-gateway uninstall   # remove the service — add --reset to also wipe local data

stop only lasts the current session: rebooting, running start, re-running setup, or an auto-upgrade all bring the daemon back. The goal is to keep the application always running; stop is primarily a developer escape hatch for debugging.

Run proxai-gateway --help to see every command.

License

MIT — see LICENSE.