PXA Control
Your rig, one click from serving
The control app for the engine: it finds your cards, reads your models from their headers, launches a server with measured settings and shows every token per second. It listens on this machine only unless you ask for the LAN, and it starts nothing until you press Start.
Every tab
Twelve tabs, captured on the test box
PXA Control v3 build (631b4ba88a) on the test box, captured 2026-10-15 with headless Chromium; server labels renamed, every number live. The screenshots follow this page's theme: switch it in the header to see the other one.
























Phone
It works on a phone
Same app, same token, laid out for a 390-pixel screen. On Android it installs as a PWA (4.0-pre, in testing).








Start it
No flags needed
./pxa # opens PXA Control in your browser
./pxa --doctor # checks cards, driver and CPU; starts nothing
./pxa --tui # the same steps in the terminal
Optional flags: --port N, --lan (listen on your network behind the access token), --no-browser, --no-tray, --models-dir DIR (remembered).
Security
A token guards the API
- On this machine the token is fresh every session and becomes an HttpOnly, SameSite=Strict cookie.
- With
--lanit is the persistent token in your config folder (mode 0600); nothing is open without it. - A POST or DELETE never takes the token from the address bar; Control scrubs it from its own logs and reports.
- Report a problem builds a report with paths, host names and addresses removed and shows you every byte before it sends.