lmstudio-ai / lmstudio-ai/mlx-engine

Image tokens not included when running Qwen3.6-35B-A3B MLX (tokens: 0, features N)

Open
#325 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1.2k
Forks
133
Avg merge
21h 6m
Merged PRs (30d)
1

Description

LM Studio version: 0.4.12 (Build 1)
Model: unsloth/Qwen3.6-35B-A3B-UD-MLX-4bit
OS: macOS (Apple Silicon)

Error

ValueError: Image features and image tokens do not match: tokens: 0, features 64

Occurs on both the native /api/v1/chat endpoint and the OpenAI-compatible /v1/chat/completions endpoint.

Repro

curl -s http://localhost:1234/api/v1/chat   -H "Content-Type: application/json"   -d '{
    "model": "qwen3.6-35b-a3b-ud-mlx",
    "input": [
      {"type": "text", "content": "What color is this square? One word."},
      {"type": "image", "data_url": "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAoAAAAKCAYAAACNMs+9AAAAFUlEQVR42mP8z8BQz0AEYBxVSF+FABJADveWkH6oAAAAAElFTkSuQmCC"}
    ],
    "temperature": 0
  }'

Context

This appears to be the same heuristic failure documented in this issue for Qwen3-VL and later Qwen 3.5-35b-a3b (fixed in 0.4.6). The Qwen 3.6 architecture (early-fused multimodal) seems to be triggering the same broken path — the vision encoder runs and produces features, but no image tokens are injected into the prompt.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Qwen3.6 multimodal request path for both /api/v1/chat and /v1/chat/completions, using the supplied curl request to reproduce the tokens: 0, features 64 mismatch. Compare that behavior with the Qwen3-VL and Qwen 3.5-35b-a3b heuristic failure referenced in the issue. Done means the image tokens and image features match for the reproduced request on both endpoints.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, machine-learning
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.