Artemis — Schneewolf Labs
A LLaVA-style graft that adds vision-language capability to any Mistral-family text decoder without modifying the decoder. Built originally for the Schneewolf Labs A-series, but architecturally Mistral-Nemo agnostic — point it at any Mistral-class checkpoint (A2, A3, Mahou, Flammades, etc.) and you get an ArtemisVLM around it.
Path B by design
PIL Image
│
▼
┌───────────────────────┐
│ Qwen3-VL ViT │ patches → ViT layers → merger
│ (FROZEN, pixels only)│
└───────────────────────┘
│ N vectors of dim out_hidden_size
▼
┌───────────────────────┐
│ Projector (trained) │ 2-layer MLP, out_hidden → text_hidden
│ ~45M params │
└───────────────────────┘
│ N vectors in the text decoder's hidden space
▼
┌───────────────────────────────────────────────────────────────┐
│ Mistral-family decoder (FROZEN in Stage-1, full-FT Stage-2) │
│ At each <|image_pad|> position, OVERWRITE the embedding with │
│ the next projector vector. Then run as a normal decoder. │
└───────────────────────────────────────────────────────────────┘
│
▼
text output (decoder's own vocab — Qwen vocab never seen)
The vision tower processes pixels (no text tokens). The projector bridges hidden spaces, not token spaces. The decoder is byte-identical to the underlying Mistral checkpoint — its vocab, weights, chat template, reasoning, tool calling, and identity are preserved by construction.
Install
pip install artemis-vlm
Or, from source:
git clone https://github.com/Schneewolf-Labs/Artemis.git
cd Artemis
pip install -e .
Requires transformers>=5.0.0, torch>=2.5.0, Pillow.
Quick start — load a pretrained Artemis checkpoint
import torch
from transformers import AutoTokenizer, AutoModelForCausalLM
import artemis_vlm # registers ArtemisVLM with AutoConfig / AutoModel
REPO = "schneewolflabs/A3-preview" # or any ArtemisVLM checkpoint
model = AutoModelForCausalLM.from_pretrained(REPO, dtype=torch.bfloat16).to("cuda").eval()
tok = AutoTokenizer.from_pretrained(REPO)
processor = artemis_vlm.ArtemisVLMProcessor(
tokenizer=tok, vision_config=model.visual.config,
min_pixels=32 * 32, max_pixels=512 * 512,
)
from PIL import Image
image = Image.open("photo.jpg")
messages = [{"role": "user", "content": [
{"type": "image"},
{"type": "text", "text": "Describe this image in detail."},
]}]
text = processor.apply_chat_template(messages, add_generation_prompt=True, tokenize=False)
batch = processor(text=text, images=[image], return_tensors="pt").to("cuda")
with torch.no_grad():
out = model.generate(**batch, max_new_tokens=200, do_sample=False)
print(tok.decode(out[0][batch["input_ids"].shape[1]:], skip_special_tokens=True))
Quick start — build a new graft from your own checkpoints
import torch
import artemis_vlm
from transformers import Qwen3VLForConditionalGeneration
# Take the vision tower from a pretrained Qwen3-VL checkpoint
qv = Qwen3VLForConditionalGeneration.from_pretrained(
"Qwen/Qwen3-VL-2B-Instruct", dtype=torch.bfloat16,
)
vision = qv.model.visual
del qv # free the Qwen3-VL decoder we don't need
# Graft onto any Mistral-class text checkpoint
model = artemis_vlm.ArtemisVLMForConditionalGeneration.from_a2_and_vision(
"schneewolflabs/A2", # or any Mistral-Nemo finetune
vision_model=vision,
image_token_id=22, # repurposed <|image_pad|> in A-series Tekken vocab
torch_dtype=torch.bfloat16,
)
# Stage-1: train only the projector (~45M params)
trainable, total = model.set_training_stage("stage1")
print(f"Stage-1: trainable={trainable/1e6:.1f}M / total={total/1e9:.2f}B")
Training (Stage-1 / Stage-2)
set_training_stage("stage1") freezes the ViT and the decoder, leaving only
the projector trainable — the "alignment" phase. set_training_stage("stage2")
unfreezes the decoder for the visual-instruction phase.
The recommended trainer is Schneewolf-Labs/Merlina,
which exposes Artemis training as training_mode: "vlm_stage1" / "vlm_stage2"
on its REST API. The ArtemisDataCollator here is data_collator=-compatible
with any trainer that consumes a custom collator (Grimoire, accelerate-driven
loops, HF Trainer).
Key implementation notes
- Merged vision features.
Qwen3VLVisionModel.forward()returns pre-merge features onlast_hidden_stateand merged features onpooler_output. We usepooler_output(matches the merger's downstream-consumer contract). - Patch / merge sizes come from
vision_config. Qwen3-VL usespatch_size=16; Qwen2-VL's image processor defaults topatch_size=14. The processor sources patch / temporal / merge fromvision_configso the<|image_pad|>expansion count can never drift from the model's merged feature count. - Image token splice. At each
<|image_pad|>position in the prompt, the input embedding is overwritten with the next projector vector (viamasked_scatter). The decoder sees a normal token sequence where some embeddings happen to come from vision instead ofembed_tokens. - DeepStack / Interleaved-MRoPE are intentionally NOT used. Those are decoder-modification ("Path A") tricks. We chose Path B (composition).
- Untied weights. A-series decoders have untied
embed_tokensandlm_head.ArtemisVLMForConditionalGeneration.all_tied_weights_keys = {}is declared explicitly for transformers 5.x compatibility.
Tests
Four hardware-bound smoke tests live in tests/. They require a real
checkpoint on disk + an ML stack + a CUDA device, so they skip cleanly under
pytest (CI won't try to run them) and are meant to be invoked as
python tests/test_artemis_<name>.py on the development machine.
python tests/test_artemis_vlm.py # model assembly + forward
python tests/test_artemis_processor.py # chat template ↔ pad expansion
python tests/test_artemis_collator.py # multimodal batching
python tests/test_artemis_stage_gen.py # staged-freeze + generate()
Published checkpoints
| Checkpoint | Status | Notes |
|---|---|---|
schneewolflabs/A3-preview |
public, apache-2.0 | 25k-sample Stage-1 smoke (proof-of-concept) |
schneewolflabs/A3 |
training (Stage-1, 1M samples) | first real release |
schneewolflabs/Artemis |
planned (post Stage-2) | named flagship |
License
Apache 2.0 — see LICENSE.
Metadata
Release files for artemis-vlm 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| artemis_vlm-0.1.4.tar.gz | 26.7 kB | With provenance | Details for artemis_vlm-0.1.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| artemis_vlm-0.1.4-py3-none-any.whl | Python 3 | none | any | Details for artemis_vlm-0.1.4-py3-none-any.whl |
Total release size: 48.0 kB
Release files / artemis_vlm-0.1.4.tar.gz
| Download URL | artemis_vlm-0.1.4.tar.gz |
|---|---|
| Size | 26.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c078e18a5a12f8e48db107870acbd6657e83e77b357a6959212083bd5313a4dc
|
|
BLAKE2b-256 checksum How to use checksums |
dc4894cf53b5a7a118841f79a443dd9109168d347b473279d921d2537d8b87c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 6, 2026.
Transparency logRelease files / artemis_vlm-0.1.4-py3-none-any.whl
| Download URL | artemis_vlm-0.1.4-py3-none-any.whl |
|---|---|
| Size | 21.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ab3c4731ea4c92aa76d2d4b1620067f937d32e411256abb7f5e7cff656ca0450
|
|
BLAKE2b-256 checksum How to use checksums |
162cbafd3b967bab660fffb1693180d1e30dc72a41974b86e880dd808f35250d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 6, 2026.
Transparency logSecurity for artemis-vlm 0.1.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for artemis_vlm-0.1.4.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 6, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.