mjolnir-cli
Serve, benchmark and document LLMs on the NVIDIA Jetson AGX Thor with
Mjolnir — a decode-attention kernel
built for Thor (sm_110), a 6-bit KV-cache format for vLLM and a patched vLLM
image that runs them. This package is the mjolnir command that drives all of
it; the kernel itself ships separately as
mjolnir-kernel.
uv tool install mjolnir-cli # or: pipx install mjolnir-cli
mjolnir hw setup # one-time Thor host setup (clocks, power mode, fans, swap)
mjolnir serve up # serve the default model on the Mjolnir image, port 6001
What it does
- Models as config dirs — every served model config is a
config.yamlofvllm serveflags (plus an optional.envof switches inside its dir; the model's calibration files sit next to the config dirs). The default configs ship inside this package; add your own under~/.local/share/mjolnir/configs/.mjolnir modelpicks the active one. - Serve —
mjolnir serve up|down|status|logsruns thenarandill/mjolnir-vllmcontainer with the active config, clears the page cache around it, and never touches a server it did not start. - Calibrate —
mjolnir calibratemeasures per-channel KV-cache scales (for the 6-bite2m3cache) and, with--draft-vocab, the drafter's vocabulary. - Benchmark —
mjolnir verify <stage>(kernel correctness and Nsight Compute benchmarks),mjolnir bench e2e|ab|perf(end-to-end serving with llama-benchy),mjolnir bench accuracy(tool-calling, GSM8K, MMLU, IFEval via tool-eval-bench). Every run waits for a clean GPU window and saves raw JSON. - Document —
mjolnir plot --readmerenders every chart, table and the README from those raw results;--sitebuilds the interactive page. - Research —
mjolnir autoresearchruns an agent loop that proposes, tests and logs kernel experiments.
Every command, with options and defaults:
the CLI reference
(generated from the commands; mjolnir <command> --help prints the same).
Requirements
A Jetson AGX Thor (JetPack 7.x) with Docker and the NVIDIA Container Toolkit
for anything that touches the GPU; Python ≥ 3.10. Charts need the plot extra
(uv tool install 'mjolnir-cli[plot]').
Versions
mjolnir-cli and mjolnir-kernel version independently; the Docker image is
tagged after the upstream vLLM it is built on (v0.31.0). Release notes:
GitHub Releases.
Metadata
Release files for mjolnir-cli 0.2.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 | |
|---|---|---|---|
| mjolnir_cli-0.2.0.tar.gz | 1.6 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mjolnir_cli-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.3 MB
Release files / mjolnir_cli-0.2.0.tar.gz
| Download URL | mjolnir_cli-0.2.0.tar.gz |
|---|---|
| Size | 1.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
53a481ff513a533ac01e783a50fc3213015b7d68ff55f5c45a8c61bd17214b35
|
|
BLAKE2b-256 checksum How to use checksums |
a5d5774e5b4180ed3079480e6989e08a18033e654375fe115b9e8c5d3bc691bc
|
| 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 15, 2026.
Transparency logRelease files / mjolnir_cli-0.2.0-py3-none-any.whl
| Download URL | mjolnir_cli-0.2.0-py3-none-any.whl |
|---|---|
| Size | 1.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6a0293359ade831cf034e07dbf86f5b817f21772c07112587b282c9002ea61b1
|
|
BLAKE2b-256 checksum How to use checksums |
c857fe5a611598f2ed979a220682f0ef2a11f64bdf8a5c834ccd343269effd0b
|
| 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 15, 2026.
Transparency log