Instructions to use RedTeamLab/Gemma-4-12B-Sol-Traces-v1 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 RedTeamLab/Gemma-4-12B-Sol-Traces-v1 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 RedTeamLab/Gemma-4-12B-Sol-Traces-v1:Q4_K_M # Run inference directly in the terminal: llama cli -hf RedTeamLab/Gemma-4-12B-Sol-Traces-v1:Q4_K_M
Install from WinGet (Windows)
winget install llama.cpp # Start a local OpenAI-compatible server with a web UI: llama serve -hf RedTeamLab/Gemma-4-12B-Sol-Traces-v1:Q4_K_M # Run inference directly in the terminal: llama cli -hf RedTeamLab/Gemma-4-12B-Sol-Traces-v1: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 RedTeamLab/Gemma-4-12B-Sol-Traces-v1:Q4_K_M # Run inference directly in the terminal: ./llama-cli -hf RedTeamLab/Gemma-4-12B-Sol-Traces-v1: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 RedTeamLab/Gemma-4-12B-Sol-Traces-v1:Q4_K_M # Run inference directly in the terminal: ./build/bin/llama-cli -hf RedTeamLab/Gemma-4-12B-Sol-Traces-v1:Q4_K_M
Use Docker
docker model run hf.co/RedTeamLab/Gemma-4-12B-Sol-Traces-v1:Q4_K_M
- LM Studio
- Jan
- Ollama
How to use RedTeamLab/Gemma-4-12B-Sol-Traces-v1 with Ollama:
ollama run hf.co/RedTeamLab/Gemma-4-12B-Sol-Traces-v1:Q4_K_M
- Unsloth Studio
How to use RedTeamLab/Gemma-4-12B-Sol-Traces-v1 with Unsloth Studio:
Install Unsloth Studio (macOS, Linux, WSL)
curl -fsSL https://unsloth.ai/install.sh | sh # Run unsloth studio unsloth studio -H 0.0.0.0 -p 8888 # Then open http://localhost:8888 in your browser # Search for RedTeamLab/Gemma-4-12B-Sol-Traces-v1 to start chatting
Install Unsloth Studio (Windows)
irm https://unsloth.ai/install.ps1 | iex # Run unsloth studio unsloth studio -H 0.0.0.0 -p 8888 # Then open http://localhost:8888 in your browser # Search for RedTeamLab/Gemma-4-12B-Sol-Traces-v1 to start chatting
Using HuggingFace Spaces for Unsloth
# No setup required # Open https://huggingface.co/spaces/unsloth/studio in your browser # Search for RedTeamLab/Gemma-4-12B-Sol-Traces-v1 to start chatting
- Pi
How to use RedTeamLab/Gemma-4-12B-Sol-Traces-v1 with Pi:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf RedTeamLab/Gemma-4-12B-Sol-Traces-v1:Q4_K_M
Configure the model in Pi
# Install Pi: npm install -g @mariozechner/pi-coding-agent # Add to ~/.pi/agent/models.json: { "providers": { "llama-cpp": { "baseUrl": "http://localhost:8080/v1", "api": "openai-completions", "apiKey": "none", "models": [ { "id": "RedTeamLab/Gemma-4-12B-Sol-Traces-v1:Q4_K_M" } ] } } }Run Pi
# Start Pi in your project directory: pi
- OpenClaw new
How to use RedTeamLab/Gemma-4-12B-Sol-Traces-v1 with OpenClaw:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf RedTeamLab/Gemma-4-12B-Sol-Traces-v1: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 "RedTeamLab/Gemma-4-12B-Sol-Traces-v1: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"
- Docker Model Runner
How to use RedTeamLab/Gemma-4-12B-Sol-Traces-v1 with Docker Model Runner:
docker model run hf.co/RedTeamLab/Gemma-4-12B-Sol-Traces-v1:Q4_K_M
- Lemonade
How to use RedTeamLab/Gemma-4-12B-Sol-Traces-v1 with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull RedTeamLab/Gemma-4-12B-Sol-Traces-v1:Q4_K_M
Run and chat with the model
lemonade run user.Gemma-4-12B-Sol-Traces-v1-Q4_K_M
List all available models
lemonade list
- Hermes Agent
How to use RedTeamLab/Gemma-4-12B-Sol-Traces-v1 with Hermes Agent:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf RedTeamLab/Gemma-4-12B-Sol-Traces-v1: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 RedTeamLab/Gemma-4-12B-Sol-Traces-v1:Q4_K_M
Run Hermes
hermes
- Atomic Chat
Gemma-4-12B-Sol-Traces-v1
Repository coding-agent model fine-tuned from unsloth/gemma-4-12B-it with LoRA on a verified original-synthetic corpus compiled from Hermes Agent session logs. The traces do not originate from OpenCode.
Verified training configuration
| Parameter | Value |
|---|---|
| Base model | unsloth/gemma-4-12B-it |
| Fine-tuning | LoRA, r=16; language + attention layers |
| Dataset | 25,000 accepted trajectories: 21,174 train / 1,324 validation / 2,502 test |
| Epochs | 1 |
| Learning rate | 1e-4, cosine schedule, 3% warmup |
| Effective batch size | 8 (2 × 4 gradient accumulation) |
| Maximum sequence length | 8,192 tokens |
| Loss | Assistant-only; tool responses excluded |
| GPU | Modal H100 80GB |
| Completed steps | 377 |
| Training loss | 0.080072 |
| Validation loss | 0.025797 |
| Runtime | 10,848 s (3h 00m 48s) |
| Peak VRAM | 46.72 GiB |
| Throughput | 1,138.7 tokens/s |
Dataset and trajectory policy
Sol Traces are compiled from Hermes Agent session logs produced while running deterministic, seed-based coding scenarios through a reference executor. The scenarios define repository templates, task requirements, and verification commands; accepted records retain the corresponding tool-use events and verification outcomes. Records are included only when their configured post-task validation succeeds.
Actual v1 coverage: 224 language/task/variant repository families across TypeScript, JavaScript, Python, shell, configuration, Go, Rust, and JVM/Java. Task categories are debugging, feature, refactoring, testing, build configuration, integration, and documentation review.
The schema defines list_files, read_file, search_code, run_command, and apply_patch. The v1 reference policy emits list_files, read_file, run_command, and apply_patch; it has no search_code calls. This model is therefore best understood as a fine-tune for the verified scripted v1 workflow, not a broadly trained autonomous coding agent.
Files
| File | Description |
|---|---|
gemma-4-12b-sol-traces-v1-Q4_K_M.gguf |
Quantized merged model (Q4_K_M) |
gemma-4-12b-sol-traces-v1-f16.gguf |
Full merged F16 model |
training_stats.json |
Full training metrics |
training_report.json |
Duplicate training report retained for compatibility |
dataset_manifest.json |
Accepted-record counts, split ratios, and rejection summary |
Usage
llama-cli \
-m gemma-4-12b-sol-traces-v1-Q4_K_M.gguf \
-ngl 99 \
--chat-template gemma \
-p "List the repository files matching *.py"
Limitations
- Fixed five-tool schema;
search_codewas not used in v1 training trajectories. - Single-trajectory sessions; no training for memory across independent conversations.
- Synthetic repository fixtures and a deterministic reference policy may not generalize to arbitrary real-world codebases.
- Downloads last month
- 150
4-bit
16-bit