Hax Web GUI
A web interface for running the hax-em programs on a GPU server from any
browser — no command line required. Fill in a form, launch a job, and watch it
run, all from the same page.
What you can do
- Run any
hax-emprogram through an auto-generated form, with the same options you'd pass on the command line — no need to remember argument names. - Launch and monitor jobs, with live logs streamed to your browser as they run.
- View training metrics with an embedded TensorBoard (the
display_metricstool). - Organise your work into projects, each keeping its own runs and output folders.
- Browse server files to pick inputs and outputs without leaving the interface.
It runs on the GPU server; your browser can be anywhere. Because everything is served from a single address, there is nothing to install in the browser — no Node, no npm, no build step.
Install
Install it into the same Conda environment that already has hax-em:
pip install hax-em-gui
This adds the hax-gui command and everything the interface needs.
Whenever a hax-em program's options change (for example after upgrading
hax-em), refresh the form definitions once:
hax-gui schemas
Run it
hax-gui start # start in the background, on http://127.0.0.1:8000
hax-gui status # is it running? where? pid + health
hax-gui restart # relaunch (keeps the current host/port)
hax-gui stop # stop it
To reach the interface from other machines, bind it to a public address:
hax-gui start --host 0.0.0.0 --port 8051
Then open http://<server>:<port> in any browser. Add --foreground
to keep the server attached to your terminal instead of running in the background.
Configuration
The server reads a few optional environment variables:
| Variable | Default | Purpose |
|---|---|---|
HAX_GUI_DATA_DIR |
~/.hax_gui |
Where job logs and the run database are stored |
HAX_GUI_FILE_ROOTS |
(unrestricted) | Colon-separated folders to confine the file browser to. Unset, it shows anything the server can read. Not a security boundary: job arguments accept any path either way |
HAX_GUI_BROWSE_HOME |
$HOME |
Folder the file browser opens at |
HAX_GUI_TOKEN |
(empty) | Shared access token. On a non-loopback bind one is always enforced: if unset, a token is generated once and kept in <data dir>/token (hax-gui start prints its location) |
HAX_GUI_ALLOWED_HOSTS |
(empty) | Extra Host header values to accept (comma-separated), for reverse-proxy setups; * disables the check. Loopback binds accept only loopback hostnames (DNS-rebinding protection) |
HAX_PROJECT_MANAGER |
hax_project_manager |
The hax-em launcher command to use |
Remote use & security
When you expose the interface beyond localhost, an access token is enforced
automatically: hax-gui start --host 0.0.0.0 generates one on first use (kept
in <data dir>/token) unless HAX_GUI_TOKEN is set. Put a reverse proxy (such
as Caddy or nginx) in front to terminate HTTPS, and set HAX_GUI_ALLOWED_HOSTS
to the public name(s) the proxy serves. The backend stays on the GPU server;
the browser can be anywhere.
On the default loopback bind the server stays open (no token) but accepts only
loopback Host headers, which blocks DNS-rebinding attacks from hostile web
pages. Set HAX_GUI_TOKEN anyway if other people can log into the machine.
Metadata
Release files for hax-em-gui 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| hax_em_gui-0.1.0.tar.gz | 1.4 MB | With provenance | Details for hax_em_gui-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| hax_em_gui-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for hax_em_gui-0.1.0-py3-none-any.whl |
Total release size: 3.0 MB
Release files / hax_em_gui-0.1.0.tar.gz
| Download URL | hax_em_gui-0.1.0.tar.gz |
|---|---|
| Size | 1.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
872e000a36c6a206a3ce3604822a68d1074086cd7bd5aa222f5b9010aad9ff3d
|
|
BLAKE2b-256 checksum How to use checksums |
94c4f8b5d1048be43dedba385f617a7c38f94472e5888bfcaecdfa7a1b1bb78c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / hax_em_gui-0.1.0-py3-none-any.whl
| Download URL | hax_em_gui-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.5 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8778d11f1079d91d4b2fdca3a795caa018ff790aab7e8599cf9c6b37deb70408
|
|
BLAKE2b-256 checksum How to use checksums |
4e3fde256a6e35973e39756e75d2db18adb8407c1b0070776f8f28a93a5d0ee8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logSecurity for hax-em-gui 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for hax_em_gui-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.