Epokio
Watch, compare, queue and report machine learning training runs from a web page, a tray icon, a terminal or the macOS menu bar. Epokio reads the files your framework already writes, so there is no logging code to add, no account and no cloud.
What it does
- See every run on this machine or a remote GPU box: state, epoch, time left, best score, curves, plain-language notes ("recall is much higher than precision…") and the result images your framework saved.
- Get told when a run finishes, fails (NaN loss), stalls or reaches a target score: on the Mac, in the tray, or as a phone push (ntfy, Slack, Discord, Telegram).
- Compare runs: only the settings that differ, a settings table for a whole sweep next to each run's main score, CSV export and Markdown reports.
- Start and queue runs (Ultralytics YOLO) from the web page, one at a time on each GPU, with a data check before
starting, a one-button Python setup (CUDA PyTorch on NVIDIA machines), resume from
weights/last.pt, and failure causes in plain words. - AI assistants can read and queue runs through the MCP server (
pip install "epokio[mcp]").
Reads Ultralytics (results.csv), Hugging Face Trainer (trainer_state.json), PyTorch Lightning
(metrics.csv), Keras (CSVLogger) and TensorBoard event files (read without TensorFlow). A hand-written
loop shows up with two lines:
import epokio
with epokio.start("runs/my-model", epochs=50, lr=1e-4) as run:
for epoch in range(50):
...
run.log(val_loss=vl, accuracy=acc)
Start
pip install epokio
epokio setup # finds your runs, starts the helper, opens the page
epokio setup --lan # also let your phone or another computer watch this machine
Other commands: epokio watch (terminal view, good over SSH), epokio tray (pip install "epokio[tray]"),
epokio doctor (what Epokio sees, for a bug report), epokio agent --stop.
Viewing is open on this machine; anything that starts, stops or changes something needs the machine's token
(epokio agent --show-token). The helper uses only the Python standard library.
MIT licence.
1 maintainer
Metadata
1 maintainer
Release files for epokio 0.5.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| epokio-0.5.3.tar.gz | 533.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| epokio-0.5.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.0 MB
Release files / epokio-0.5.3.tar.gz
| Download URL | epokio-0.5.3.tar.gz |
|---|---|
| Size | 533.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
599edb24252d48029a8dfd2986c86ca18391f88edfaae9c90d8bf5a5cf25c031
|
|
BLAKE2b-256 checksum How to use checksums |
12ccf4a1a185d3be4a629c477c363b296ca1d366c268f69506247fb8323f0812
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 1, 2026.
Transparency logRelease files / epokio-0.5.3-py3-none-any.whl
| Download URL | epokio-0.5.3-py3-none-any.whl |
|---|---|
| Size | 480.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
870db5d0c3a4b460dccd00127b3354095cb8d3cd08fad9daf0751d189d775773
|
|
BLAKE2b-256 checksum How to use checksums |
de2d7de38f52c5ec9d4a60578e86a0d56a5488696cce9065b9b90ca234653366
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 1, 2026.
Transparency log
