hexa-forge-code-3b-Q5_K_M-GGUF-v0.2.0-r11
hexa-forge-code-3b-Q5_K_M-GGUF-v0.2.0-r11 is a 3 billion parameter chat model from dancinlab, released May 11, 2026. hexa-forge-code-3b-Q5_K_M-GGUF-v0.2.0-r11 is an open-weights chat model with roughly 3 billion parameters.
by dancinlab · 3B parameters
Best for
- low-latency chat and routing
- request routing and triage
- text classification
Ways to use hexa-forge-code-3b-Q5_K_M-GGUF-v0.2.0-r11 in osFoundry
Connect with your own key (BYOK)
Open the key dialog and paste your dancinlab API key. osFoundry discovers hexa-forge-code-3b-Q5_K_M-GGUF-v0.2.0-r11 automatically — assign it to a Maestro role (router, direct, orchestrator, or fallback) in the Pipeline tab and it is live in every chat. Your key, your provider account — no token markup.
Deploy a dedicated endpoint
hexa-forge-code-3b-Q5_K_M-GGUF-v0.2.0-r11 is open-weights — run it locally for free, or deploy a dedicated GPU endpoint in your workspace for reserved capacity with no rate limits.
Use it in a Room App
Room Apps declare AI features in their manifest, then call them with invokeAI:
import { invokeAI } from '@osfoundry/app-sdk'
// 'summarize' is an AI feature declared in your app manifest.
const result = await invokeAI('summarize', userText)
Call it from your own apps
Once a model is wired into your workspace you can host it as an API and reach it from your own services, scripts, or CI — outside osFoundry.
What hardware can run hexa-forge-code-3b-Q5_K_M-GGUF-v0.2.0-r11
hexa-forge-code-3b-Q5_K_M-GGUF-v0.2.0-r11 runs on a single 16GB consumer GPU (~2 GB VRAM with KV-cache headroom). Full-precision inference fits on a single H100 80GB at FP16 precision (~8 GB).
hexa-forge-code-3b-Q5_K_M-GGUF-v0.2.0-r11 vs similar models
Licence
Unspecified — Licence terms not specified — verify the upstream model card before commercial use.
Check upstream documentation.
Frequently asked about hexa-forge-code-3b-Q5_K_M-GGUF-v0.2.0-r11
Is hexa-forge-code-3b-Q5_K_M-GGUF-v0.2.0-r11 free to use?
hexa-forge-code-3b-Q5_K_M-GGUF-v0.2.0-r11 is free to run locally on your own hardware. Hosted access through osFoundry is metered (input Free (local), output Free (local)). You can switch between local and hosted at any time.
Can I use hexa-forge-code-3b-Q5_K_M-GGUF-v0.2.0-r11 commercially?
Commercial use is allowed with conditions. Licence terms not specified — verify the upstream model card before commercial use. Check upstream documentation.
How much VRAM does hexa-forge-code-3b-Q5_K_M-GGUF-v0.2.0-r11 need?
Approximately 2 GB at Q4 quantisation, or 8 GB at full FP16 precision. Fits on a single 24GB consumer GPU.
Can I run hexa-forge-code-3b-Q5_K_M-GGUF-v0.2.0-r11 locally?
Yes. hexa-forge-code-3b-Q5_K_M-GGUF-v0.2.0-r11 is open-weights and runs locally on a workstation GPU. osFoundry's local runtime handles model loading, quantisation, and routing.
What is hexa-forge-code-3b-Q5_K_M-GGUF-v0.2.0-r11 best at?
hexa-forge-code-3b-Q5_K_M-GGUF-v0.2.0-r11 is well-suited to low-latency chat and routing, request routing and triage, text classification.
How do I use hexa-forge-code-3b-Q5_K_M-GGUF-v0.2.0-r11 in osFoundry?
Paste your dancinlab API key in the key dialog (or deploy the open weights for self-hostable models), assign hexa-forge-code-3b-Q5_K_M-GGUF-v0.2.0-r11 to a Maestro role in the Pipeline tab, then use it in chat, Room Apps via invokeAI, or your own apps.
Published by dancinlab on May 11, 2026. Source: https://huggingface.co/dancinlab/hexa-forge-code-3b-Q5_K_M-GGUF-v0.2.0-r11