Instructions to use ccore/Qwen3.5-4B-3D-Coder 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 ccore/Qwen3.5-4B-3D-Coder 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 ccore/Qwen3.5-4B-3D-Coder:Q4_K_M # Run inference directly in the terminal: llama cli -hf ccore/Qwen3.5-4B-3D-Coder:Q4_K_M
Install from WinGet (Windows)
winget install llama.cpp # Start a local OpenAI-compatible server with a web UI: llama serve -hf ccore/Qwen3.5-4B-3D-Coder:Q4_K_M # Run inference directly in the terminal: llama cli -hf ccore/Qwen3.5-4B-3D-Coder: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 ccore/Qwen3.5-4B-3D-Coder:Q4_K_M # Run inference directly in the terminal: ./llama-cli -hf ccore/Qwen3.5-4B-3D-Coder: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 ccore/Qwen3.5-4B-3D-Coder:Q4_K_M # Run inference directly in the terminal: ./build/bin/llama-cli -hf ccore/Qwen3.5-4B-3D-Coder:Q4_K_M
Use Docker
docker model run hf.co/ccore/Qwen3.5-4B-3D-Coder:Q4_K_M
- LM Studio
- Jan
- Ollama
How to use ccore/Qwen3.5-4B-3D-Coder with Ollama:
ollama run hf.co/ccore/Qwen3.5-4B-3D-Coder:Q4_K_M
- Unsloth Desktop
- Pi
How to use ccore/Qwen3.5-4B-3D-Coder with Pi:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf ccore/Qwen3.5-4B-3D-Coder: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": "ccore/Qwen3.5-4B-3D-Coder:Q4_K_M" } ] } } }Run Pi
# Start Pi in your project directory: pi
- Docker Model Runner
How to use ccore/Qwen3.5-4B-3D-Coder with Docker Model Runner:
docker model run hf.co/ccore/Qwen3.5-4B-3D-Coder:Q4_K_M
- Lemonade
How to use ccore/Qwen3.5-4B-3D-Coder with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull ccore/Qwen3.5-4B-3D-Coder:Q4_K_M
Run and chat with the model
lemonade run user.Qwen3.5-4B-3D-Coder-Q4_K_M
List all available models
lemonade list
- Hermes Agent
How to use ccore/Qwen3.5-4B-3D-Coder with Hermes Agent:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf ccore/Qwen3.5-4B-3D-Coder: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 ccore/Qwen3.5-4B-3D-Coder:Q4_K_M
Run Hermes
hermes
- Atomic Chat
- OpenClaw
How to use ccore/Qwen3.5-4B-3D-Coder with OpenClaw:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf ccore/Qwen3.5-4B-3D-Coder: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 "ccore/Qwen3.5-4B-3D-Coder: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"
Feedback loop
The model makes many mistakes like undefined variables which it could catch itself if it had a feedback loop. I'd suggest downloading headless Chrome to run the code and catch any errors, and then rendering the scene to a file (maybe with multiple viewing angles) and then ingesting the image file to check whether it looks right.
I tried to build such a feedback loop myself using unsloths mmproj, but the model got stuck repeating itself. It might help to add feedback loops to the training data.
Another idea to improve the training with feedback loops is to corrupt a good scene and instruct the model to fix it.
yeah, you're right about those issues. i'm seeing around a 60% one-shot success rate on complex scenes so far. sometimes it generates unused variables or declares the same variable twice and breaks the code, especially at higher temperatures
i'm finishing another checkpoint today and then moving on to rl, where the model will get feedback from actually running and rendering the scenes
the errors you mentioned definitely happen, and i'm hoping the feedback loop will help reduce them. i also like your idea of training it to fix intentionally broken scenes
yeah, you're right about those issues. i'm seeing around a 60% one-shot success rate on complex scenes so far. sometimes it generates unused variables or declares the same variable twice and breaks the code, especially at higher temperatures
i decided to release this early because, compared to the base 4b model, which struggled to even generate a decent chair in my tests, this already felt like a pretty big step forward. but training is still ongoing
i'm finishing another checkpoint today and then moving on to rl, where the model will get feedback from actually running and rendering the scenes
the errors you mentioned definitely happen, and i'm hoping the feedback loop will help reduce them. i also like your idea of training it to fix intentionally broken scenes