Instructions to use MarxistLeninist/Qwen3.8-27B-IQ1_M-GGUF 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 MarxistLeninist/Qwen3.8-27B-IQ1_M-GGUF 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 MarxistLeninist/Qwen3.8-27B-IQ1_M-GGUF:IQ1_M # Run inference directly in the terminal: llama cli -hf MarxistLeninist/Qwen3.8-27B-IQ1_M-GGUF:IQ1_M
Install from WinGet (Windows)
winget install llama.cpp # Start a local OpenAI-compatible server with a web UI: llama serve -hf MarxistLeninist/Qwen3.8-27B-IQ1_M-GGUF:IQ1_M # Run inference directly in the terminal: llama cli -hf MarxistLeninist/Qwen3.8-27B-IQ1_M-GGUF:IQ1_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 MarxistLeninist/Qwen3.8-27B-IQ1_M-GGUF:IQ1_M # Run inference directly in the terminal: ./llama-cli -hf MarxistLeninist/Qwen3.8-27B-IQ1_M-GGUF:IQ1_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 MarxistLeninist/Qwen3.8-27B-IQ1_M-GGUF:IQ1_M # Run inference directly in the terminal: ./build/bin/llama-cli -hf MarxistLeninist/Qwen3.8-27B-IQ1_M-GGUF:IQ1_M
Use Docker
docker model run hf.co/MarxistLeninist/Qwen3.8-27B-IQ1_M-GGUF:IQ1_M
- LM Studio
- Jan
- vLLM
How to use MarxistLeninist/Qwen3.8-27B-IQ1_M-GGUF with vLLM:
Install from pip and serve model
# Install vLLM from pip: pip install vllm # Start the vLLM server: vllm serve "MarxistLeninist/Qwen3.8-27B-IQ1_M-GGUF" # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:8000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "MarxistLeninist/Qwen3.8-27B-IQ1_M-GGUF", "messages": [ { "role": "user", "content": [ { "type": "text", "text": "Describe this image in one sentence." }, { "type": "image_url", "image_url": { "url": "https://cdn.britannica.com/61/93061-050-99147DCE/Statue-of-Liberty-Island-New-York-Bay.jpg" } } ] } ] }'Use Docker
docker model run hf.co/MarxistLeninist/Qwen3.8-27B-IQ1_M-GGUF:IQ1_M
- Ollama
How to use MarxistLeninist/Qwen3.8-27B-IQ1_M-GGUF with Ollama:
ollama run hf.co/MarxistLeninist/Qwen3.8-27B-IQ1_M-GGUF:IQ1_M
- Unsloth Desktop
- Pi
How to use MarxistLeninist/Qwen3.8-27B-IQ1_M-GGUF with Pi:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf MarxistLeninist/Qwen3.8-27B-IQ1_M-GGUF:IQ1_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": "MarxistLeninist/Qwen3.8-27B-IQ1_M-GGUF:IQ1_M" } ] } } }Run Pi
# Start Pi in your project directory: pi
- Docker Model Runner
How to use MarxistLeninist/Qwen3.8-27B-IQ1_M-GGUF with Docker Model Runner:
docker model run hf.co/MarxistLeninist/Qwen3.8-27B-IQ1_M-GGUF:IQ1_M
- Lemonade
How to use MarxistLeninist/Qwen3.8-27B-IQ1_M-GGUF with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull MarxistLeninist/Qwen3.8-27B-IQ1_M-GGUF:IQ1_M
Run and chat with the model
lemonade run user.Qwen3.8-27B-IQ1_M-GGUF-IQ1_M
List all available models
lemonade list
- Hermes Agent
How to use MarxistLeninist/Qwen3.8-27B-IQ1_M-GGUF with Hermes Agent:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf MarxistLeninist/Qwen3.8-27B-IQ1_M-GGUF:IQ1_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 MarxistLeninist/Qwen3.8-27B-IQ1_M-GGUF:IQ1_M
Run Hermes
hermes
- Atomic Chat
- OpenClaw
How to use MarxistLeninist/Qwen3.8-27B-IQ1_M-GGUF with OpenClaw:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf MarxistLeninist/Qwen3.8-27B-IQ1_M-GGUF:IQ1_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 "MarxistLeninist/Qwen3.8-27B-IQ1_M-GGUF:IQ1_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"
Qwen3.8-27B IQ1_M agentic and tool-call validation
This directory preserves both the original failed Ollama result and the repaired controller-plus-model result. The evidence is deliberately additive: the old 0/6 report remains relevant to raw Ollama compatibility, while the new validation shows a reproducible way to obtain native structured tool_calls from the same model file.
Result
| Path | Result | Meaning |
|---|---|---|
| Ollama 0.32.14 OpenAI-compatible tool interface | 0/6 | The intended calls appeared as ordinary assistant text and tool_calls remained null. |
Direct llama.cpp with one selected tool and tool_choice="required" |
1/1 | Native structured tool_calls serialization works. |
Direct llama.cpp with three available tools and tool_choice="required" |
0/1 | Raw IQ1_M multi-tool selection repeated argument text and reached the token limit without a tool call. |
Adapter with three available tools and tool_choice="auto" |
6/6 | Weather, calculator and note requests returned the correct function and exact JSON arguments. |
Adapter with OpenAI named tool_choice object |
1/1 | The object form was normalized and returned weather({"city":"Berlin"}) as a native tool call. |
The repaired path therefore passes the tested explicit tool-use cases. It does not turn the raw quant into an unrestricted semantic router: the adapter contributes deterministic tool selection, then asks the model runtime to serialize the chosen call.
Root cause
The investigation separated three issues that the original 0/6 score had bundled together:
- The tested llama.cpp build expects
tool_choiceas a string. It rejects the OpenAI named-object form when sent directly. - The IQ1_M quant can emit a proper structured call when one selected tool is presented.
- Raw selection across several tools is unreliable at this quantization level and runtime configuration.
ADAPTER.py repairs the integration boundary rather than changing or requantizing the model.
Adapter behaviour
The adapter is a small standard-library OpenAI-compatible proxy. It:
- defaults to loopback-only binding;
- accepts the OpenAI named
tool_choiceobject and normalizes it; - scores explicit user wording against tool names, descriptions and parameter names;
- presents only the selected tool to llama.cpp with
tool_choice="required"; - preserves llama.cpp's native
tool_callsresponse; - can retry once when raw model content identifies exactly one available function;
- contains no credentials, remote-control features or external network dependencies.
For ambiguous requests where no tool clearly wins, the adapter does not invent a selection. A stronger semantic router can replace the scoring function without changing the downstream serialization path.
Reproduce
Requirements:
- the repository's
Qwen3.8-27B-IQ1_M.gguffile; - a llama.cpp
llama-serverbuild compatible with Qwen3.8 and Jinja tool templates; - Python 3.10 or newer;
curlfor the launcher health checks.
Start the local runtime and adapter:
chmod +x AGENTIC_VALIDATION/RUN_AGENTIC_ADAPTER.sh
LLAMA_SERVER=/path/to/llama-server \
AGENTIC_VALIDATION/RUN_AGENTIC_ADAPTER.sh
The default OpenAI-compatible endpoint is:
http://127.0.0.1:18540/v1/chat/completions
Send the included request:
curl -sS http://127.0.0.1:18540/v1/chat/completions \
-H 'Content-Type: application/json' \
--data-binary @AGENTIC_VALIDATION/REQUEST_EXAMPLE.json
The response should have finish_reason: "tool_calls" and a weather call containing {"city":"Tokyo"}.
Validation configuration
- Model:
Qwen3.8-27B-IQ1_M.gguf - Model SHA-256:
131cdf5c1c4b547081543382b00434e9ebf3f8eb369ef3714550086074f80bdf - Runtime: llama.cpp
b9591-62061f910 - Chat template: Jinja,
peg-native - Reasoning: disabled, budget 0
- Context: 1,024 tokens
- Temperature: 0
- Adapter bind: loopback only
- Validation host: CPU-only GETH
The CPU-only timing was slow: the six cases took 1,019.264 seconds in total, with individual cases between 150.487 and 194.198 seconds. Those timings demonstrate correctness under constrained hardware, not production throughput. The earlier RTX 3090 ordinary-generation result remains the relevant acceleration measurement.
Files
ADAPTER.py: OpenAI-compatible tool-selection and normalization proxy.RUN_AGENTIC_ADAPTER.sh: one-command local launcher for llama.cpp plus the adapter.REQUEST_EXAMPLE.json: two-tool example request.SUMMARY.json: concise machine-readable result and scope.ADAPTER_VALIDATION.json: full six-case results, arguments, timings and usage.NAMED_TOOL_CHOICE_VALIDATION.json: live OpenAI named-object compatibility result.RAW_RUNTIME_FINDINGS.json: direct runtime diagnosis and preserved Ollama result.CHECKSUMS.sha256: hashes for every file in this directory.
Interpretation and limits
The useful conclusion is narrower than “the 1-bit model is fully agentic” and much stronger than “the quant cannot use tools.” The exact model can serialize valid structured calls, but its raw multi-tool routing is brittle. A lightweight controller that chooses one explicit tool produces reliable structured output in the tested cases.
The tests cover explicit weather, arithmetic and note requests. They do not establish performance on ambiguous instructions, large overlapping tool catalogues, adversarial schemas, multi-call planning or long tool-result continuations.
Publication hygiene
This directory is sanitized for public release. It contains no API keys, access tokens, passwords, private keys, authorization headers, private network addresses, environment dumps or user-specific data.