Instructions to use bottlecapai/ThinkingCap-Qwen3.8-Flash-Next-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 bottlecapai/ThinkingCap-Qwen3.8-Flash-Next-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 bottlecapai/ThinkingCap-Qwen3.8-Flash-Next-GGUF:Q4_K_M # Run inference directly in the terminal: llama cli -hf bottlecapai/ThinkingCap-Qwen3.8-Flash-Next-GGUF:Q4_K_M
Install from WinGet (Windows)
winget install llama.cpp # Start a local OpenAI-compatible server with a web UI: llama serve -hf bottlecapai/ThinkingCap-Qwen3.8-Flash-Next-GGUF:Q4_K_M # Run inference directly in the terminal: llama cli -hf bottlecapai/ThinkingCap-Qwen3.8-Flash-Next-GGUF:Q4_K_M
Build from source code
git clone https://github.com/ggml-org/llama.cpp.git cd llama.cpp cmake -B build cmake --build build -j --target llama-app # Start a local OpenAI-compatible server with a web UI: ./build/bin/llama serve -hf bottlecapai/ThinkingCap-Qwen3.8-Flash-Next-GGUF:Q4_K_M # Run inference directly in the terminal: ./build/bin/llama cli -hf bottlecapai/ThinkingCap-Qwen3.8-Flash-Next-GGUF:Q4_K_M
Use Docker
docker model run hf.co/bottlecapai/ThinkingCap-Qwen3.8-Flash-Next-GGUF:Q4_K_M
- Llama new
- LM Studio
- Jan
- vLLM
How to use bottlecapai/ThinkingCap-Qwen3.8-Flash-Next-GGUF with vLLM:
Install from pip and serve model
# Install vLLM from pip: pip install vllm # Start the vLLM server: vllm serve "bottlecapai/ThinkingCap-Qwen3.8-Flash-Next-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": "bottlecapai/ThinkingCap-Qwen3.8-Flash-Next-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/bottlecapai/ThinkingCap-Qwen3.8-Flash-Next-GGUF:Q4_K_M
- Ollama
How to use bottlecapai/ThinkingCap-Qwen3.8-Flash-Next-GGUF with Ollama:
ollama run hf.co/bottlecapai/ThinkingCap-Qwen3.8-Flash-Next-GGUF:Q4_K_M
- Unsloth Desktop
- Pi
How to use bottlecapai/ThinkingCap-Qwen3.8-Flash-Next-GGUF with Pi:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf bottlecapai/ThinkingCap-Qwen3.8-Flash-Next-GGUF: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": "bottlecapai/ThinkingCap-Qwen3.8-Flash-Next-GGUF:Q4_K_M" } ] } } }Run Pi
# Start Pi in your project directory: pi
- Docker Model Runner
How to use bottlecapai/ThinkingCap-Qwen3.8-Flash-Next-GGUF with Docker Model Runner:
docker model run hf.co/bottlecapai/ThinkingCap-Qwen3.8-Flash-Next-GGUF:Q4_K_M
- Lemonade
How to use bottlecapai/ThinkingCap-Qwen3.8-Flash-Next-GGUF with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull bottlecapai/ThinkingCap-Qwen3.8-Flash-Next-GGUF:Q4_K_M
Run and chat with the model
lemonade run user.ThinkingCap-Qwen3.8-Flash-Next-GGUF-Q4_K_M
List all available models
lemonade list
- Hermes Agent
How to use bottlecapai/ThinkingCap-Qwen3.8-Flash-Next-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 bottlecapai/ThinkingCap-Qwen3.8-Flash-Next-GGUF: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 bottlecapai/ThinkingCap-Qwen3.8-Flash-Next-GGUF:Q4_K_M
Run Hermes
hermes
- Atomic Chat
- OpenClaw
How to use bottlecapai/ThinkingCap-Qwen3.8-Flash-Next-GGUF with OpenClaw:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf bottlecapai/ThinkingCap-Qwen3.8-Flash-Next-GGUF: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 "bottlecapai/ThinkingCap-Qwen3.8-Flash-Next-GGUF: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"
Request: GSQ-RCO ThinkingCap GGUFs in collaboration with ISTA-DASLab
Hi Bottlecap team,
I’ve been running ThinkingCap-Qwen3.8-Flash-Next Q4_K_M locally through XeStrata on Linux, on a Threadripper 3970X with 128 GB RAM and a Radeon RX 6900 XT with 16 GB VRAM. ThinkingCap’s shorter reasoning is particularly appealing for this kind of local setup.
Would you consider collaborating with ISTA-DASLab to release GSQ-RCO GGUFs of ThinkingCap, or exploring another method with a comparable quality-to-size trade-off?
Their Qwen3.8-Flash-Next GSQ-RCO release reports:
- 75.8 GB (IQ3_XXS): 99.4% of the BF16 base’s average benchmark score across AIME25, GPQA-Diamond and LiveCodeBench v6.
- 83.6 GB (IQ3_S): approximately BF16-level scores on that suite.
For comparison, your current ThinkingCap GGUFs weigh 95.5 GB for IQ4_XS and 113.2 GB for the recommended Q4_K_M.
Those results wouldn’t automatically carry over to the fine-tuned weights, but combining a smaller footprint with ThinkingCap’s reported 38.5% average reduction in reasoning tokens would be compelling for local users like me.
A comparison showing total download size, resident memory requirements, benchmark-score retention and reasoning-token savings for each quantization under matched evaluation settings would be especially useful. It would help establish whether the smaller versions preserve both answer accuracy and ThinkingCap’s shorter reasoning.
Is this something you would consider?
Hi!
Such a collab is not currently planned, but here is an IQ3_S RCO build for now. We also tried making the XXS variant, but that one already prolonged thinking traces too much compared to the full-precision checkpoint.
I've also added the usual Expected performance section to this model's GGUF cards. It took a bit longer in this case due to the size of the model and the amount of checkpoints to evaluate. Hope that provides the info you need.