Instructions to use Local-Axiom-AI/Sabaki-Preview 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 Local-Axiom-AI/Sabaki-Preview 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 Local-Axiom-AI/Sabaki-Preview:F16 # Run inference directly in the terminal: llama cli -hf Local-Axiom-AI/Sabaki-Preview:F16
Install from WinGet (Windows)
winget install llama.cpp # Start a local OpenAI-compatible server with a web UI: llama serve -hf Local-Axiom-AI/Sabaki-Preview:F16 # Run inference directly in the terminal: llama cli -hf Local-Axiom-AI/Sabaki-Preview:F16
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 Local-Axiom-AI/Sabaki-Preview:F16 # Run inference directly in the terminal: ./llama-cli -hf Local-Axiom-AI/Sabaki-Preview:F16
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 Local-Axiom-AI/Sabaki-Preview:F16 # Run inference directly in the terminal: ./build/bin/llama-cli -hf Local-Axiom-AI/Sabaki-Preview:F16
Use Docker
docker model run hf.co/Local-Axiom-AI/Sabaki-Preview:F16
- LM Studio
- Jan
- vLLM
How to use Local-Axiom-AI/Sabaki-Preview with vLLM:
Install from pip and serve model
# Install vLLM from pip: pip install vllm # Start the vLLM server: vllm serve "Local-Axiom-AI/Sabaki-Preview" # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:8000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "Local-Axiom-AI/Sabaki-Preview", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }'Use Docker
docker model run hf.co/Local-Axiom-AI/Sabaki-Preview:F16
- Ollama
How to use Local-Axiom-AI/Sabaki-Preview with Ollama:
ollama run hf.co/Local-Axiom-AI/Sabaki-Preview:F16
- Unsloth Desktop
- Pi
How to use Local-Axiom-AI/Sabaki-Preview with Pi:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf Local-Axiom-AI/Sabaki-Preview:F16
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": "Local-Axiom-AI/Sabaki-Preview:F16" } ] } } }Run Pi
# Start Pi in your project directory: pi
- Docker Model Runner
How to use Local-Axiom-AI/Sabaki-Preview with Docker Model Runner:
docker model run hf.co/Local-Axiom-AI/Sabaki-Preview:F16
- Lemonade
How to use Local-Axiom-AI/Sabaki-Preview with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull Local-Axiom-AI/Sabaki-Preview:F16
Run and chat with the model
lemonade run user.Sabaki-Preview-F16
List all available models
lemonade list
- Hermes Agent
How to use Local-Axiom-AI/Sabaki-Preview with Hermes Agent:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf Local-Axiom-AI/Sabaki-Preview:F16
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 Local-Axiom-AI/Sabaki-Preview:F16
Run Hermes
hermes
- Atomic Chat
- OpenClaw
How to use Local-Axiom-AI/Sabaki-Preview with OpenClaw:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf Local-Axiom-AI/Sabaki-Preview:F16
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 "Local-Axiom-AI/Sabaki-Preview:F16" \ --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"
Runaway generation mechanics, rotary phase mismatch, and state dissipation in 3:1 KDA-MLA hybrids
Hi Local-Axiom-AI team,
Pretraining a custom 221.5M 3:1 hybrid (12 KDA recurrent layers, 4 latent-attention MLA layers) with Top-2/8 MoE from scratch across 8B tokens, and shipping a custom GGUF runtime with honest documentation of the runaway generation failure mode, is fantastic systems work. The sample efficiency against 125M baselines on just 8B tokens confirms the representational power of the 3:1 macro-topology.
Looking at your architectural schedule and the runaway generation issue:
Rotary phase mismatch in intermittent MLA:
Your schedule interleaves 3 KDA blocks with 1 rotary MLA block. KDA updates its recurrent state in continuous coordinate space without positional phase rotation. Injecting RoPE specifically at the MLA layers introduces an alternating phase projection: representations must repeatedly transition between rotation-invariant recurrent updates and frequency-rotated attention manifolds.
This periodic coordinate torsion makes it difficult for the network to establish sharp delimiter boundaries, which directly contributes to the model failing to emit EOS after completing a response.Residual state retention and attractor basins:
In a recurrent backbone, finishing an answer leaves non-zero activation energy in the KDA state matrices. In standard attention, trailing tokens can cleanly attend back to a prompt-level boundary to fire an EOS logit. But when 75% of depth is linear recurrence, if the attention layers lack an explicit salience-isolation mechanism, background sequence momentum keeps propagating through the recurrent state. The model cannot dissipate this residual energy, pushing generation into the runaway nonsensical loops you observed.The 22.4% active vocabulary footprint:
With a 49,152 byte-level BPE vocabulary at hidden size 768, the tied embedding table consumes 37.75M parameters.
Against your 130.7M active non-embedding parameters, static token lookup accounts for 22.4% of your total forward compute budget per token. Decoupling or factorizing token embeddings would free up substantial parameter capacity to expand your routed expert count without changing inference latency.Resolving runaway dynamics via NoPE and bounded indexing:
In an open architecture project called Maba v2 (reference release: https://huggingface.co/AndrewThompson1233/maba-v2-architecture), which shares this exact 3:1 macro-balance between linear recurrence and sparse attention:
We eliminated positional phase conflict entirely by running native NoPE across all layers, relying on recurrent state progression for sequence order.
To prevent residual runaway loops, we paired the recurrent backbone with MABA-SA (a sparse attention mechanism with anti-dilution indexing). This cleanly isolates delimiter signals from lingering recurrent activation noise, guaranteeing clean EOS termination without runaway wandering.
If you are planning a Sabaki v2 or another post-training pass, checking out the hybrid coordination and state management layout in the Maba v2 repo might provide some practical reference points for stabilizing generation boundaries.
Did the runaway generation behavior emerge primarily during the 4,096-token curriculum stage, or was it already pronounced during the 512 base pretrain?
Best,
Andrew
Andrew,
We released this model as a feedback tool, and we greatly appreciate your feed back and it will be taking into consideration you suggestions for a newer release. After some basic testing we found out that it was likely just the post training because during the post training we did train in the full 16k context and one of the datasets might have included the behavior that we all have seen. We are currently working on a non preview version of this model that should be done training in a few months that currently has none of the repeat problems and tends to be an overall better on topic model.
Local-Axiom-AI team
Hi Local-Axiom-AI team,
That makes total sense! Context elongation during post-training is notorious for this - if long-sequence datasets have truncated endings, trailing padding, or inconsistent EOS supervision, the model quickly learns that sequence continuation is always prioritized over termination.
Isolating the issue to the 16k post-training data is great news, as it means your core 3:1 KDA-MLA hybrid backbone is fundamentally sound. Scaling an MoE hybrid like this from scratch is ambitious, and having clean generation without repetition loops in the upcoming full run will be huge.
Best of luck with the training run over the next few months! Looking forward to testing the production checkpoint when it drops.
Best,
Andrew