Instructions to use jlebthedude/n64dllm-v1 with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Notebooks
- Google Colab
- Kaggle
- Local Apps Settings
- llama.cpp
How to use jlebthedude/n64dllm-v1 with llama.cpp:
Install (macOS, Linux)
curl -LsSf https://llama.app/install.sh | sh # Start a local OpenAI-compatible server with a web UI: llama serve -hf jlebthedude/n64dllm-v1:Q4_K_M # Run inference directly in the terminal: llama cli -hf jlebthedude/n64dllm-v1:Q4_K_M
Install from WinGet (Windows)
winget install llama.cpp # Start a local OpenAI-compatible server with a web UI: llama serve -hf jlebthedude/n64dllm-v1:Q4_K_M # Run inference directly in the terminal: llama cli -hf jlebthedude/n64dllm-v1:Q4_K_M
Use pre-built binary
# Download pre-built binary from: # https://github.com/ggerganov/llama.cpp/releases # Start a local OpenAI-compatible server with a web UI: ./llama-server -hf jlebthedude/n64dllm-v1:Q4_K_M # Run inference directly in the terminal: ./llama-cli -hf jlebthedude/n64dllm-v1:Q4_K_M
Build from source code
git clone https://github.com/ggerganov/llama.cpp.git cd llama.cpp cmake -B build cmake --build build -j --target llama-server llama-cli # Start a local OpenAI-compatible server with a web UI: ./build/bin/llama-server -hf jlebthedude/n64dllm-v1:Q4_K_M # Run inference directly in the terminal: ./build/bin/llama-cli -hf jlebthedude/n64dllm-v1:Q4_K_M
Use Docker
docker model run hf.co/jlebthedude/n64dllm-v1:Q4_K_M
- LM Studio
- Jan
- vLLM
How to use jlebthedude/n64dllm-v1 with vLLM:
Install from pip and serve model
# Install vLLM from pip: pip install vllm # Start the vLLM server: vllm serve "jlebthedude/n64dllm-v1" # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:8000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "jlebthedude/n64dllm-v1", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }'Use Docker
docker model run hf.co/jlebthedude/n64dllm-v1:Q4_K_M
- Ollama
How to use jlebthedude/n64dllm-v1 with Ollama:
ollama run hf.co/jlebthedude/n64dllm-v1:Q4_K_M
- Unsloth Studio
How to use jlebthedude/n64dllm-v1 with Unsloth Studio:
Install Unsloth Studio (macOS, Linux, WSL)
curl -fsSL https://unsloth.ai/install.sh | sh # Run unsloth studio unsloth studio -H 0.0.0.0 -p 8888 # Then open http://localhost:8888 in your browser # Search for jlebthedude/n64dllm-v1 to start chatting
Install Unsloth Studio (Windows)
irm https://unsloth.ai/install.ps1 | iex # Run unsloth studio unsloth studio -H 0.0.0.0 -p 8888 # Then open http://localhost:8888 in your browser # Search for jlebthedude/n64dllm-v1 to start chatting
Using HuggingFace Spaces for Unsloth
# No setup required # Open https://huggingface.co/spaces/unsloth/studio in your browser # Search for jlebthedude/n64dllm-v1 to start chatting
- Pi
How to use jlebthedude/n64dllm-v1 with Pi:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf jlebthedude/n64dllm-v1:Q4_K_M
Configure the model in Pi
# Install Pi: npm install -g @earendil-works/pi-coding-agent # Add to ~/.pi/agent/models.json: { "providers": { "llama-cpp": { "baseUrl": "http://localhost:8080/v1", "api": "openai-completions", "apiKey": "none", "models": [ { "id": "jlebthedude/n64dllm-v1:Q4_K_M" } ] } } }Run Pi
# Start Pi in your project directory: pi
- Docker Model Runner
How to use jlebthedude/n64dllm-v1 with Docker Model Runner:
docker model run hf.co/jlebthedude/n64dllm-v1:Q4_K_M
- Lemonade
How to use jlebthedude/n64dllm-v1 with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull jlebthedude/n64dllm-v1:Q4_K_M
Run and chat with the model
lemonade run user.n64dllm-v1-Q4_K_M
List all available models
lemonade list
- Hermes Agent
How to use jlebthedude/n64dllm-v1 with Hermes Agent:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf jlebthedude/n64dllm-v1:Q4_K_M
Configure Hermes
# Install Hermes: curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash hermes setup # Point Hermes at the local server: hermes config set model.provider custom hermes config set model.base_url http://127.0.0.1:8080/v1 hermes config set model.default jlebthedude/n64dllm-v1:Q4_K_M
Run Hermes
hermes
- Atomic Chat
- OpenClaw
How to use jlebthedude/n64dllm-v1 with OpenClaw:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf jlebthedude/n64dllm-v1:Q4_K_M
Configure OpenClaw
# Install OpenClaw: npm install -g openclaw@latest # Register the local server and set it as the default model: openclaw onboard --non-interactive --mode local \ --auth-choice custom-api-key \ --custom-base-url http://127.0.0.1:8080/v1 \ --custom-model-id "jlebthedude/n64dllm-v1:Q4_K_M" \ --custom-provider-id llama-cpp \ --custom-compatibility openai \ --custom-text-input \ --accept-risk \ --skip-health
Run OpenClaw
openclaw agent --local --agent main --message "Hello from Hugging Face"
n64dllm-v1
A LoRA fine-tune of Qwen3-Coder-30B-A3B-Instruct for N64 matching decompilation: given MIPS assembly, write C that recompiles byte-identically under the original SGI IDO 5.3/7.1 compilers. Trained on roughly 74k examples mined from 11 community decomp projects. Every training pair was verified by recompiling it with the original compiler and byte-comparing against the shipped ROM, and every number below is judged the same way. No similarity metrics anywhere.
Results
Held-out games the model never trained on (Pokemon Snap, Mischief Makers), identical prompts for all models, byte-exact recompilation as the judge:
| Model | exact match @1 | pass@8 |
|---|---|---|
| Qwen3-Coder-30B-A3B, stock | 6.7% | |
| n64dllm-v1, this Q4_K_M file | 18.3% | 20.0% |
| Claude Opus 4.8 | 20.0% |
The MoE base has 3.3B active parameters, so this runs at about 90 tok/s on an M4 Max. Cheap sampling plus a compiler oracle is the intended usage pattern.
Files
n64dllm-v1-Q4_K_M.gguf: for llama.cpp, LM Studio, or any GGUF runtime. Quantization was gated by re-running the benchmark on this exact file; it lost nothing vs bf16.adapter/: the LoRA (rank 64, attention projections) if you want to keep training.
Usage
llama-server -m n64dllm-v1-Q4_K_M.gguf --port 8081 -ngl 99 -c 16384 --jinja -fa on
The prompt format matters. Supply the declared prototype from the project's headers; in ablation it was worth 11.7 points:
You are an expert N64 matching-decompilation model. Given MIPS assembly produced by the ido5.3 compiler, output C that recompiles to a byte-identical match.
; compiler: ido5.3
; declared prototype: void func_80123456(Actor* this, s32 arg1);
; target assembly:
<output of objdump -dr --disassemble=<fn> on the target object>
; matching C:
You will get the best results inside an agent harness with the compiler in the loop: sample several candidates, recompile each, byte-compare, feed diffs back. The project repo ships a ready-made skill file for Codex and OpenCode plus a verification harness built on n64-decomp-workbench.
Limitations
Function signatures should be supplied, not guessed; cross-game struct internals are the main remaining failure mode. Assembly beyond ~4k tokens was not trained on. v1 covers IDO games only, not the GCC-family titles. General coding ability of the base survives the fine-tune (the LoRA touches attention projections only), and tool calling works.
Intended use
Research and community decompilation assistance. Matching decompilation is an existing community practice aimed at interoperability and preservation; this model writes new C and contains no game assets. Not for commercial use of decompiled output. The training data is not distributed.
- Downloads last month
- 39
4-bit
Model tree for jlebthedude/n64dllm-v1
Base model
Qwen/Qwen3-Coder-30B-A3B-Instruct