Model guide

Qwen3.6 35B-A3B on Mac: memory and coding setup

Keep your coding client and choose a memory budget for a growing chat. Start with the MLX profile, then check the window admitted on your Mac.

A long stone arcade has a few orange-lit arches among many quiet openings.
MLX download 19.3 GB
MLX admitted window 229,376 tokens
MLX window estimate 55.2 GB · estimated

Key facts

Reference Mac: Apple M1 Max · 32-core GPU · 64 GB. Decode is engine-reported tokens per second; other Macs are not measured.

mxfp4 · editor's choice

Qwen3.6 35B-A3B

Engine
MLX
Download
19.3 GB
Admitted window
229,376 tokens
Memory: measured or estimated
55.2 GB · estimated
Measured depth and window estimate
Measured to 131,443 tokens (39.1 GB peak, M1 Max 64 GB). The 229,376-token window is estimated at 55.2 GB.
Short decode
94.8–98.6 tok/sconditions not recorded
Decode at depth
47.1 tok/sconditions not recorded
SWE-bench Verified (base weights)
73.4 creatorconditions not recorded
Catalog date
2026-10-09

GGUF UD-Q3_K_M

Qwen3.6 35B-A3B MTP

Engine
GGUF / llama.cpp
Download
17.1 GB
Admitted window
262,144 tokens
Memory: measured or estimated
27.0 GB · estimated
Short decode
55.6–63.1 tok/sconditions not recorded
Decode at depth
35.0 tok/sconditions not recorded
SWE-bench Verified (base weights)
not measured
Catalog date
2026-10-09

Compare profiles in the model catalog

Start with the MLX row

Select Qwen3.6 35B-A3B, MLX mxfp4, in Bridge1. Check memory before loading it. The catalog marks this profile as an Editor’s Choice; it is not the default coding model.

The 35B name counts all parameters. Qwen reports about 3B active parameters per token, but that smaller active count does not make this a 3B-sized download or memory footprint.

Qwen3.6-35B-A3B MLX mxfp4 showing an automatic 229,376-token context window out of 262,144, approximate start memory of 21 GB and growth of 1.4 GB per 10K tokens, and a DFlash2 drafter.

Swipe to see the whole row

The memory pill gives approximate start memory and growth; the context label shows an automatic limit of 229,376 out of 262,144 tokens.

Figure 1. Apple M1 Max, 64 GB. Read the automatic 229,376-token window and the approximate memory pill: about 21 GB to start, plus 1.4 GB per 10K tokens. “Fast” and “est. 1m 10s cold start at 36K” are the app’s own label and estimate for this Mac, not Bridge1 measurements. The 55.2 GB window estimate is in figure 2. · v0.7.5 ·

A download size is only the beginning

Measured to 131,443 tokens (39.1 GB peak, M1 Max 64 GB). The 229,376-token window is estimated at 55.2 GB.

The catalog is dated 2026-10-09. The reference Apple M1 Max has a 32-core GPU. Your Mac’s memory budget can admit a different window.

Model weights stay in memory while attention state grows with the conversation. Leave room for macOS and your coding client as well. Do not subtract the 19.3 GB download from 55.2 GB and call the difference a measured cache size: those numbers describe different things.

Figure 1 shows the app’s approximate memory labels: about 21 GB to start, plus 1.4 GB per 10K tokens. These approximations are not measurements. Figure 2 labels the 55.2 GB figure at the default window as estimated; it does not predict a safe chat length for a smaller Mac.

Choose a smaller catalog model when keeping your editor and other apps open leaves too little memory for this profile’s admitted window. On a 32 GB Mac, the 64 GB reference result is a reason to reduce the window or choose less demanding weights, not a promise that the same long chat will fit.

Common scale: 0–60 GB

Qwen3.6 35B-A3B

mxfp4 · editor's choice · MLX

Download size
19.3 GB
Catalog memory estimate
55.2 GB estimated
Measured peak at this window
not measured
Admitted window
229,376 tokens

Catalog date:

The GGUF build

GGUF UD-Q3_K_M · GGUF / llama.cpp

Download size
17.1 GB
Catalog memory estimate
27.0 GB estimated
Measured peak at this window
not measured
Admitted window
262,144 tokens

Catalog date:

The MLX download is 19.3 GB; its admitted window is 229,376 tokens, with estimated memory of 55.2 GB at that window. The app’s approximate start memory and growth labels appear in figure 1. Download size and running memory describe different quantities.

Figure 2. Reference Mac: Apple M1 Max, 32-core GPU, 64 GB. Catalog dated 2026-10-09. Both window totals are estimated; the recorded MLX measurement stops at a shorter depth.
Your coding client connects through Bridge1 to Qwen3.6 on the same Mac.A client sends requests through the local gateway to the model. Memory holds weights and growing attention state, with room also needed for macOS and your apps. Box sizes are not memory proportions.SHARED MAC MEMORYYour coding clientBridge1 gatewayQwen3.6 35B-A3BModel weightsGrowing attention statemacOS + your apps
Figure 3. Keep your coding client; budget memory for the model and the conversation together.

Choose the model, then copy Gateway setup

On macOS, bridge1 launch starts Claude Code, Codex, OpenCode or Pi with Bridge1, subject to the installed client version, model availability and loading settings; the manual steps still work. Open the Gateway panel after selecting the model. Copy the setup for your client, including the generated model name and context settings. Route1 follows the model selected in Bridge1; use the native name supplied there when you want to target one model directly.

For Claude Code, the base URL is http://127.0.0.1:54321, without a /v1 suffix. The command below comes from the Claude Code setup guide and uses a placeholder key. Copy Gateway’s full command for your selected model, including its extra context setting for windows of 100,000 tokens or more. OpenCode and Codex use a base URL ending in /v1; follow their guides below.

ANTHROPIC_BASE_URL="http://127.0.0.1:54321" \
ANTHROPIC_API_KEY="YOUR-GATEWAY-KEY" \
ANTHROPIC_MODEL="claude-route1" \
API_TIMEOUT_MS="1800000" \
CLAUDE_STREAM_IDLE_TIMEOUT_MS="2400000" \
CLAUDE_CODE_DISABLE_NONSTREAMING_FALLBACK="1" \
ANTHROPIC_CUSTOM_HEADERS="X-Bridge1-Client: claude-code" \
claude

This example uses claude-route1 and a placeholder key. Copy the complete Gateway command for your selected model to keep its timeout and context settings.

Figure 4. Claude Code launch command. Replace YOUR-GATEWAY-KEY with your own key; the base URL has no /v1 suffix.

When to consider the GGUF build

The GGUF UD-Q3_K_M build runs through llama.cpp. It is a separate choice in Bridge1: 17.1 GB on disk, a 262,144-token admitted window and 27.0 GB estimated memory on the reference Mac.

Consider this build when its smaller catalog memory estimate fits your budget better. Keep the estimated label in view. It is not a measured 27 GB requirement, and the build’s name alone does not establish a speed advantage or equal coding quality between the two quantizations.

The Qwen3.6-35B-A3B GGUF UD-Q3_K_M build showing a full 262,144-token context window and a memory pill marked 27.0 GB at 262,144 tokens, est.

Swipe to see the whole row

The memory pill marks 27.0 GB at 262,144 tokens as estimated.

Figure 5. Qwen3.6 35B-A3B MTP (GGUF, UD-Q3_K_M) on Apple M1 Max, 64 GB. Read the full 262,144-token window and the “27.0 GB at 262,144 tokens · est.” memory pill; “est.” means estimated memory. “Medium · this Mac” and “est. 1m 10s cold start at 36K” are the app’s own label and estimate for this Mac, not Bridge1 measurements. · v0.7.5 ·

What the coding evidence answers

As of 26 September 2026, Bridge1’s published task evaluation recorded 38 passes out of 40 for Qwen3.6 35B-A3B through Claude Code. Those were small Python repositories, with hidden tests; the result does not establish the same behavior in a large project or every client.

The catalog’s decode figures measure output generation. They do not include the whole wait to read a long prompt or finish a coding task. Use the Speed page for that distinction and the Evidence page for the test conditions; the key facts above preserve missing conditions rather than turning token rates into a response-time promise.

Qwen’s original model page declares Apache-2.0. The MLX Community mxfp4 page and Unsloth GGUF page each declare Apache-2.0 too. The three linked references identify those artifacts separately, accessed 2026-10-19.

Connect your client

OpenCode setup

  1. Merge the generated bridge1 provider entry into your OpenCode configuration and select bridge1/route1 or its supplied plain model id.
  2. Preserve attachment and modalities fields when present. OpenCode cannot see token usage in Bridge1 replies yet, so keep an eye on long chats instead of relying on automatic compaction.

Pi.dev setup

  1. Early support covers one short smoke-test turn only. Copy the generated custom-provider JSON and verify the chosen model before use.
  2. Preserve input, contextWindow and maxTokens when supplied; without contextWindow, Pi assumes 128,000 tokens.

Codex setup

  1. Copy the generated provider configuration. Keep wire_api set to responses and the base URL ending in /v1.
  2. Use route1 or the plain model id shown by Gateway. For Codex Desktop, save the same provider configuration as the CLI, then quit and reopen the app.

Hermes Agent setup

  1. Early support covers one smoke-test turn only. Add a custom endpoint with the Gateway values, then Test and Save.
  2. Keep the generated vision and context values. Without supports_vision, Hermes sends a text description of an image instead of the image.

Claude Code setup

  1. Select this model for Route1, then copy the Claude Code launch command from Gateway and run it in your project folder with your own gateway key.
  2. Keep claude-route1, the generated timeout settings and the extra context setting included for windows of 100,000 tokens or more.

Claude Desktop setup

  1. Download config.json from Gateway and import it with New → Import in Claude Desktop’s configurations switcher. Select Bridge1, restart and use Test connection.
  2. The Code tab can give up after about 13 minutes without visible output. Its first step on a new prompt rereads the chat: about 2.5 minutes at 53K tokens was observed on Qwen3.6 35B-A3B; later steps reused it.

Limits

Check client support and known limits

Questions

Does the Qwen3.6 download size tell me how much memory I need?

No. The download covers the model file. Running memory also grows with the conversation, and your apps need room. Use the estimated memory at the admitted window on the reference Mac to plan, then check the window selected on your own Mac.

Plan your Mac memory budget

When should I consider the Qwen3.6 GGUF profile?

Consider GGUF when its catalog memory estimate fits your budget better. That estimate is not a measured requirement or evidence of equal coding quality between profiles. Select the profile before copying client settings from Gateway.

Check Qwen3.6 catalog profiles

Sources

  1. Qwen3.6 35B-A3B — Apache-2.0 declared by Qwen · Accessed
  2. MLX Community mxfp4 — Apache-2.0 declared · Accessed
  3. Unsloth GGUF build — Apache-2.0 declared · Accessed
  4. Bridge1 model catalog: reference Mac and memory labels · Accessed
  5. Bridge1 coding task evaluation: conditions and limits · Accessed

Make room for local coding

Check your Mac.
Choose your model.