Over recent months, we have intensified our focus on developing foundation models that deliver exceptional utility and performance.
Mage-VL-Cowork
microsoft·Instruct·released 30 Oct 2026
hf download microsoft/Mage-VL-CoworkMage-VL-Cowork A Full Training Recipe to Learn Hybrid Computer Use from Evolved Harnesses
How much VRAM does Mage-VL-Cowork need?
At Q4_K_M Mage-VL-Cowork needs about 4.4 GB with an 8K context (4.4 GB at Q4, 11 GB at full precision). Pick your GPU to see what fits and how fast it runs.
Needs: ≈4.3 GB · Q4_K_M · 8K context — Pick a GPU to check the fit.
Advanced: context 8K · KV cache 16-bit
Smallest GPU for each quant and context (KV cache 16-bit)
| Quantisation | 8K | 16K | 32K | 64K | 128K | 256K |
|---|---|---|---|---|---|---|
| Q3_K_M | ||||||
| Q4_K_M | ||||||
| Q5_K_M | ||||||
| Q6_K | ||||||
| Q8_0 | ||||||
| FP16 |
≤16 GB card24–32 GB48–96 GBmore
| Quantisation | Total |
|---|---|
| Q2_KHeavy lossSmallest, noticeably worse quality | ≈3.1 GB |
| Q3_K_MNoticeable lossSmall, some quality loss | ≈3.9 GB |
| Q4_K_MrecommendedSmall lossRecommended default for local use | ≈4.3 GB |
| Q5_K_MNear-losslessNear-lossless for most tasks | ≈4.9 GB |
| Q6_KNear-losslessPractically lossless | ≈5.4 GB |
| Q8_0LosslessLossless in practice, twice the size of Q4 | ≈6.2 GB |
| FP16 / BF16LosslessFull precision, as released | ≈10 GB |
Estimates for 8K tokens of context: weights + KV cache + runtime overhead. Speed assumes memory-bound decoding at your GPU’s bandwidth. Pick a GPU above and the fit column checks every row against it. Weights marked “file” use the real GGUF download size; “est.” rows are computed from the parameter count.
How to pick a quant
Take the biggest quant that fits with room left for context. Q4_K_M is the usual sweet spot. Below Q4 quality drops fast, above Q6 you mostly pay memory for nothing. Big models (70B+, large MoE) tolerate low quants better than small ones.
- LosslessF16, Q8_0
- Near-losslessQ6_K, Q5_K_M
- Small lossQ5_K_S, Q4_K_M, IQ4_NL, IQ4_XS, Q4_K_S
- Noticeable lossQ4_0, Q3_K_L, Q3_K_M, IQ3_M
- Heavy lossIQ3_XXS, Q3_K_S, IQ2_M, Q2_K
Typical quality loss, not measured per model. Tiers come from KL divergence against FP16 on Llama 3 8B: llama.cpp perplexity README: LLaMA 3 8B scoreboard (KLD and ΔPPL vs FP16, Wikitext-2); llama.cpp quantize tool: ΔPPL per quant type @ Llama-3-8B
How much context fits?
At 8K context, Q4_K_M needs ≈4.3 GB(2.5 GB weights + 1.1 GB KV cache + 0.6 GB overhead). Pick a GPU above to see how much context fits.
Weights + overheadKV cache
Can the RTX 4060 run Mage-VL-Cowork? →
Speed vs quality per quant
Smaller quants run faster and fit in less memory, but lose quality.
Fits in VRAMTight fitCPU offload✕ won't runQuality is typical KL divergence vs FP16, not measured for this model.
Real-world speed of Mage-VL-Cowork
Tokens per second measured by people running it at home. A GPU shows a median once 3 reports agree on the same setup. Reports far from our estimate wait for a review. Measure yours with llama-bench →
No medians yet. Be one of the first 3 to report a setup.
All reports
Run Mage-VL-Cowork locally
These commands load the original weights from Hugging Face.
from transformers import pipeline
pipe = pipeline("image-text-to-text", model="microsoft/Mage-VL-Cowork", dtype="auto", device_map="auto")
messages = [
{
"role": "user",
"content": [
{"type": "image", "url": "https://huggingface.co/datasets/huggingface/documentation-images/resolve/main/bee.jpg"},
{"type": "text", "text": "Describe this image."},
],
}
]
out = pipe(text=messages, max_new_tokens=256)
print(out[0]["generated_text"][-1]["content"])Quantised versions and downloads
| Repository | Format | Quant | Size |
|---|---|---|---|
| ggml-org/Mage-VL-Cowork-GGUF | GGUF | Q4_K_M | 2.7 GB |
| ggml-org/Mage-VL-Cowork-GGUF | GGUF | Q8_0 | 4.7 GB |
| ggml-org/Mage-VL-Cowork-GGUF | GGUF | BF16 | 8.8 GB |
| Hansda/Mage-VL-Cowork-GGUF | GGUF | — | — |
| maternion/Mage-VL-Cowork-4B-GGUF | GGUF | — | — |
| Pragmaticl/Mage-VL-Cowork-GGUF | GGUF | — | — |
| pratikgx/Mage-VL-Cowork-MLX-4bit | MLX | 4BIT | — |
| netprojects/Mage-VL-Cowork-MLX-6bit | MLX | 6BIT | — |
| netprojects/Mage-VL-Cowork-MLX-8bit | MLX | 8BIT | — |
| netprojects/Mage-VL-Cowork-MLX-bf16 | MLX | BF16 | — |
About Mage-VL-Cowork
Mage-VL-Cowork A Full Training Recipe to Learn Hybrid Computer Use from Evolved Harnesses --- One compact 4B policy that knows when to click — and when to code. Computer-use agents (CUAs) that confine themselves to pixels pay a heavy tax: a single screenshot consumes thousands of tokens, and re-deriving structured file edits through dozens of mouse clicks discards the fastest, most verifiable channel on the machine. Conversely, giving a frontier model naive access to both GUI and terminal tools does not automatically produce hybrid competence — without an optimized execution scaffold, even frontier teachers exhibit suboptimal channel habits that transfer directly to distilled students. Worse, existing CUA post-training pipelines rely on checkpoints already heavily specialized for GUI grounding and coding. Mage-VL-Cowork bridges this gap. Trained end-to-end from an intermediate 4B Mage-VL checkpoint through a progressive five-stage specialize-then-unify curriculum, it combines screenshot-grounded GUI interaction (computer_use) and persistent code/terminal execution (bash) inside a single vision-language policy — with no external orchestrator. Upstream of training, we evolve the teacher harness (pruning redundant action routes and equipping domain libraries) and build Mage-CUA-Forge, a workflow-first synthesis engine that generates 293,806 tasks across 6,915 atomic skills while cutting recurring per-task generation cost by 82.6%.
Full model card on Hugging Face →Alternatives to Mage-VL-Cowork
All alternatives →Meet Qwen3-VL — the most powerful vision-language model in the Qwen series to date.
Over recent months, we have intensified our focus on developing foundation models that deliver exceptional utility and performance.
WeVisOne-VL (WeChat Vision All-in-One) is a unified vision-language model developed by WeChat Vision, Tencent Inc. Built upon Qwen3-VL, it unifies object-level perception (open-vocabulary object detection, referring localization, object counting, object pointing, and OCR) and pixel-level perception…
H2O-Lightning-4B is a 4B-parameter decision model from H2O.ai, built on Qwen/Qwen3.5-4B. It answers typed decision questions about a record (a document, a ticket, a policy, a conversation) and about images that come with the record (photos, screenshots, scanned documents, charts).
* License: The use of MedGemma is governed by the Health AI Developer Foundations terms of use. MedGemma has not been evaluated or optimized for multi-turn applications.
Mage-VL-Cowork FAQ
- How much VRAM does Mage-VL-Cowork need?
- About 4.4 GB at Q4_K_M with an 8K context. Q8_0 needs about 6.5 GB and full precision about 11 GB. Longer contexts need more memory for the KV cache.
- Can Mage-VL-Cowork run on the RTX 4060?
- Yes. It fits at Q8_0 (about 6.2 GB), at an estimated 30 tokens/s. It fits comfortably on the Apple M4 (16 GB), Radeon RX 6700 XT, RTX 3060 12GB.
- Can I use Mage-VL-Cowork commercially?
- Yes. It is released under Apache 2.0. Permissive: use, modify and sell freely; keep the notice and licence text.
- What is the context length of Mage-VL-Cowork?
- 262,144 tokens (256K). The full window needs far more memory than an 8K context.
- How do I run Mage-VL-Cowork locally?
- It runs with Transformers. Each has copy-paste examples in its docs.
Rate this model
Data from Hugging Face, the model card and public leaderboards. Memory and speed figures are estimates; real numbers depend on the runtime, context length and drivers. Always check the licence yourself before commercial use.
0 comments