Who it is forA developer or tinkerer who wants to see the boot and chat flow on a Linux machine before writing to any USB stick.
The problemFlashing the wrong device or debugging boot problems on real hardware is slow and risky, so an emulator check comes first.
The outcomeA built nightrun.img that boots in a QEMU window and shows the NightRun chat with live status.
What you need first
- A Linux machine with Rust stable and nightly installed
- About 6 GB of free disk for a model plus the image
- A USB stick (x86_64 target) or microSD card (Raspberry Pi 5 target), or QEMU for testing without hardware
- For real hardware: a 64-bit UEFI x86_64 PC with Secure Boot off, or a Raspberry Pi 5
Steps
- Run
git clone https://github.com/hardrave/NIGHTRUN.gitand thencd NIGHTRUN. - Run
curl -L -o models/Llama-3.2-1B-Instruct-Q8_0.gguf https://huggingface.co/bartowski/Llama-3.2-1B-Instruct-GGUF/resolve/main/Llama-3.2-1B-Instruct-Q8_0.gguf. (inferred, check the README) - Run
cargo run --release -p nrconvert -- models/Llama-3.2-1B-Instruct-Q8_0.gguf models/model.nrmto convert the model to .nrm. (inferred, check the README) - Run
cargo xtask image --model models/model.nrmto build nightrun.img. - Run
cargo xtask run --img --mem 4G --windowto boot the image in QEMU.
Prompt for your agent
Use the repo hardrave/NIGHTRUN to convert the model at <target> (a GGUF file path) into models/model.nrm and boot it in QEMU with cargo xtask run --img --mem 4G --window. Expected output: a QEMU window showing the NightRun chat prompt. Verify the nrconvert step reports that it re-validated its own output before you boot.
Caveat. The README lists QEMU as the test path and notes that QEMU rows in its benchmarks come from single scripted runs, so QEMU speed is not a guarantee for real hardware.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page