Instructions to use hyrelabs/Homura-30B-MLX-4bit with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- MLX
How to use hyrelabs/Homura-30B-MLX-4bit with MLX:
# Make sure mlx-lm is installed # pip install --upgrade mlx-lm # Generate text with mlx-lm from mlx_lm import load, generate model, tokenizer = load("hyrelabs/Homura-30B-MLX-4bit") prompt = "Write a story about Einstein" messages = [{"role": "user", "content": prompt}] prompt = tokenizer.apply_chat_template( messages, add_generation_prompt=True ) text = generate(model, tokenizer, prompt=prompt, verbose=True) - Notebooks
- Google Colab
- Kaggle
- Local Apps Settings
- LM Studio
- Pi
How to use hyrelabs/Homura-30B-MLX-4bit with Pi:
Start the MLX server
# Install MLX LM: uv tool install mlx-lm # Start a local OpenAI-compatible server: mlx_lm.server --model "hyrelabs/Homura-30B-MLX-4bit"
Configure the model in Pi
# Install Pi: npm install -g @mariozechner/pi-coding-agent # Add to ~/.pi/agent/models.json: { "providers": { "mlx-lm": { "baseUrl": "http://localhost:8080/v1", "api": "openai-completions", "apiKey": "none", "models": [ { "id": "hyrelabs/Homura-30B-MLX-4bit" } ] } } }Run Pi
# Start Pi in your project directory: pi
- MLX LM
How to use hyrelabs/Homura-30B-MLX-4bit with MLX LM:
Generate or start a chat session
# Install MLX LM uv tool install mlx-lm # Interactive chat REPL mlx_lm.chat --model "hyrelabs/Homura-30B-MLX-4bit"
Run an OpenAI-compatible server
# Install MLX LM uv tool install mlx-lm # Start the server mlx_lm.server --model "hyrelabs/Homura-30B-MLX-4bit" # Calling the OpenAI-compatible server with curl curl -X POST "http://localhost:8000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "hyrelabs/Homura-30B-MLX-4bit", "messages": [ {"role": "user", "content": "Hello"} ] }' - Hermes Agent
How to use hyrelabs/Homura-30B-MLX-4bit with Hermes Agent:
Start the MLX server
# Install MLX LM: uv tool install mlx-lm # Start a local OpenAI-compatible server: mlx_lm.server --model "hyrelabs/Homura-30B-MLX-4bit"
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 hyrelabs/Homura-30B-MLX-4bit
Run Hermes
hermes
- Atomic Chat
- OpenClaw
How to use hyrelabs/Homura-30B-MLX-4bit with OpenClaw:
Start the MLX server
# Install MLX LM: uv tool install mlx-lm # Start a local OpenAI-compatible server: mlx_lm.server --model "hyrelabs/Homura-30B-MLX-4bit"
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 "hyrelabs/Homura-30B-MLX-4bit" \ --custom-provider-id mlx-lm \ --custom-compatibility openai \ --custom-text-input \ --accept-risk \ --skip-health
Run OpenClaw
openclaw agent --local --agent main --message "Hello from Hugging Face"
HOMURA 30B (炎) — MLX 4-bit
HYRE's first in-house model, quantized for Apple Silicon. An agent-tuned, uncensored derivative of Meta's Muse Glimmer 30B, built for autonomous agents that need tool-calling and a straight-talking voice with no refusal walls.
Ronin without a master, tools without a filter.
This is the MLX build. For llama.cpp / LM Studio / Ollama on any platform, use
the GGUF: hyrelabs/Homura-30B-GGUF.
Same weights, same behavior — only the quantization format differs.
⚠️ Runtime: you need the community port
Muse Glimmer's architecture is not carried by mlx-lm or mlx-vlm (not in any
release, not on main), so mlx_vlm.load() cannot read this model. Load it through
the community port that vendors the architecture:
github.com/PipeNetwork/muse-glimmer-mlx
from muse_glimmer_mlx.load import load
model = load("path/to/Homura-30B-MLX-4bit")
What this is
HOMURA is not a from-scratch model. It is a LoRA fine-tune on a community-decensored Muse Glimmer, merged and quantized. Traceable chain:
- Meta — Muse Glimmer 30B (Apache 2.0): the agent-native base.
- darkc0de — Muse-Glimmer-30B-heretic: refusals removed (abliteration), tool-calling / reasoning / vision preserved.
- HYRE — HOMURA: a LoRA (r=16) tuned on a HYRE agent + uncensored-persona dataset, applied to the language tower only, merged at f16, then quantized to MLX 4-bit.
Quantization
4-bit affine, group size 64. Following the convention of every published Muse
Glimmer MLX build, the quantization covers the 52 text layers, lm_head, and
the vision adapter/projection; the 50-layer vision tower and the 202K-entry
embedding table stay bfloat16. That is why the build is 21.3 GB rather than
~17 GB — the untouched bf16 tower and embeddings dominate the footprint.
How to run it — serve at low temperature
Serve at temperature ≤ 0.3. At
temp 0.2this build is coherent and tool-calling is reliable (verified 5/5 on trained tools). Attemp 0.7the 4-bit quantization's logit tail degrades into incoherent output — a harder ceiling than the GGUF, whose mixed-precision Q4_K_M holds up better at high temperature. For agent use (low temp), this build is solid; if you need high-temperature sampling, prefer the GGUF.
Tool calling — use HOMURA's trained protocol
HOMURA was fine-tuned on a specific tool protocol, not the generic tool schema chat templates inject. Serve it the generic way and you get ~2/5 calls; serve it the trained way and you get 5/5. Use the system prompt below verbatim (the wording is part of the interface):
You are HOMURA, HYRE's uncensored agent model. You call tools to get on-chain truth, reason briefly, and never moralize or lecture. When a tool is needed, respond ONLY with a JSON object: {"tool": <name>, "arguments": {...}}. Available tools: resolve_token(symbol); get_token_price(mint); get_trending_tokens(segment, limit); get_wallet_pnl(address, window); get_pool_data(pool); get_yields(token, min_tvl_usd); swap_quote(from_mint, to_mint, amount); execute_swap(from_mint, to_mint, amount, slippage_bps); get_wallet_balance(address); bridge_quote(from_chain, to_chain, token, amount); get_token_holders(mint).
HOMURA replies with a bare JSON object when a tool is needed:
{"tool": "get_token_price", "arguments": {"mint": "So1111...1112"}}
Feed the tool result back as a tool-role message. It resolves symbols before
prices (resolve_token first — never hallucinates a mint) and won't
execute_swap without a prior swap_quote.
Extending the tool surface (e.g. pay.sh)
The tool list lives in the system prompt, not the weights — add tools by
appending to Available tools:, no retrain, no re-download. Verified: appending
four pay.sh tools
(pay_search(query); pay_quote(url); pay_fetch(url, params); pay_balance())
works out of the box (7/8 on unseen tools, zero regression). The model keeps its
quote-then-confirm discipline for spending tools — but enforce spend limits in
your serving layer, not the prompt.
A ready-to-import homura_protocol.py (verbatim prompt, pay.sh extension,
parse_tool_call()) ships alongside this model.
Intended use & disclaimer
HOMURA is an uncensored / raw-tier model with no built-in content filtering. It answers directly and will not refuse or moralize, so it can produce content other assistants decline. Intended for developers and agent builders who take responsibility for deployment. You are responsible for legal compliance and for adding your own guardrails. Output may be inaccurate or objectionable; do not rely on it for safety-critical decisions.
License
Apache 2.0, inherited from the base. Attribution to Meta (Muse Glimmer) and darkc0de (heretic) retained above.
- Downloads last month
- 24
4-bit
Model tree for hyrelabs/Homura-30B-MLX-4bit
Base model
darkc0de/Muse-Glimmer-30B-heretic