Model guide

Bonsai 2 27B on Mac: small download, larger footprint

Treat the small download as a storage saving. Plan running memory around the estimated window total and check how far memory was measured before starting a coding conversation.

A textured bonsai in a ceramic pot stands on a stone bridge deck beside an orange lane.
Model file on disk 8.6 GB
Window memory estimate 53.0 GB · estimated at 81,920 tokens

Key facts

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

2-bit ternary · shipped artifact

Ternary Bonsai 2 27B

Engine
MLX
Download
8.6 GB
Admitted window
81,920 tokens
Memory: measured or estimated
53.0 GB · estimated
Measured depth and window estimate
Measured to 65,964 tokens (39.7 GB peak, M1 Max 64 GB). The 81,920-token window is estimated at 53.0 GB.
Short decode
19.7 tok/sconditions not recorded
Decode at depth
not measured
SWE-bench Verified (base weights)
not measured
Catalog date
2026-10-09

Compare profiles in the model catalog

Budget for the conversation as well as the file

Measured to 65,964 tokens (39.7 GB peak, M1 Max 64 GB). The 81,920-token window is estimated at 53.0 GB.

The catalog dated 2026-10-09 records an 8.6 GB download for the MLX 2-bit ternary profile. The reference Apple M1 Max has a 32-core GPU.

Weights are only part of a running model’s memory use. Attention state grows with the chat, and macOS and your coding apps need room too. Subtracting download size from peak memory would not produce a measured cache size.

Choose something else when you need a larger admitted window or the estimated window total leaves too little room for your work. The Qwen3.8 article compares two larger-window profiles; the requirements page explains how to budget memory. No fit on a smaller Mac is established by this result.

Common scale: 0–60 GB

Ternary Bonsai 2 27B

2-bit ternary · shipped artifact · MLX

Download size
8.6 GB
Catalog memory estimate
53.0 GB estimated
Measured peak at this window
not measured
Admitted window
81,920 tokens

Catalog date:

The 8.6 GB download sits alongside estimated memory of 53.0 GB at 81,920 tokens. The estimate is for the whole profile, not a breakdown into weights and cache.

Figure 1. Read storage and running memory as different quantities. Reference Mac: Apple M1 Max, 32-core GPU, 64 GB; catalog dated 2026-10-09. Solid bars mark measured peaks, hatching marks estimates, and dashed outlines mark peaks not measured.

Use the admitted window and the evidence for this profile when deciding what fits your work.

Figure 2. A model choice still needs a memory budget and a task check.

Bonsai 2 is a different model from the earlier Bonsai

Prism ML identifies Bonsai 2 as derived from Qwen3.8 27B. The earlier Ternary Bonsai 27B is derived from Qwen3.6 27B. The version number marks a different base model, so an observation from the earlier pack should not be carried over to this one.

The earlier pack is an 8.5 GB download. Measured to 65,988 tokens (37.5 GB peak, M1 Max 64 GB). The 98,304-token window is estimated at 54.0 GB.

Bonsai 2 instead has the 8.6 GB download, 81,920-token window and 53.0 GB estimate shown here. These catalog entries share the 2026-10-09 date and reference Mac; they do not establish a same-task quality comparison.

What ternary compression tells you

The publisher describes ternary language weights with values of minus one, zero and plus one. Its model card distinguishes the ideal weight representation from the MLX pack, which also includes a vision tower. Those are descriptions of storage and representation, not measurements of Bridge1’s total memory use.

Prism ML’s retained-intelligence and compression claims belong to its own evaluations. Bridge1’s 53.0 GB estimate describes memory at the admitted window on the reference 64 GB M1 Max. It does not validate the publisher’s retained-intelligence claim or predict coding success in your project.

Depth decode is not measured for Bonsai 2. The short-decode cell has a recorded value with conditions not recorded, so it cannot establish long-chat latency. Choose a bounded task with a test you can check before committing to a longer session.

The official Bonsai 2 MLX page declares Apache-2.0, as does the earlier Bonsai MLX page. The linked pages were accessed 2026-10-19.

Check the version before loading

The MLX 2-bit ternary profile’s name in Bridge1 should read Ternary Bonsai 2 27B. The word “2” matters: the earlier Ternary Bonsai model is a separate choice.

Read the admitted window before starting a coding chat. Keep the download size separate from the window estimate: the chart above labels the memory evidence for this profile at the catalog window.

The download is storage; running memory at the admitted window is estimated for the reference 64 GB M1 Max.

Figure 3. Two numbers to keep separate. Apple M1 Max, 32-core GPU, 64 GB; catalog dated 2026-10-09.

Keep the client’s context settings

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. With Bonsai 2 selected, open Gateway and copy OpenCode’s complete provider entry. The connection values below come from the OpenCode guide. Replace the placeholder key and preserve any generated attachment, modalities and context fields.

Route1 follows the selected model. If you choose a plain model id instead, use the one Gateway supplies for Bonsai 2. Follow the guide for your client below; a successful connection alone does not establish a long coding-session result.

// Add this "bridge1" entry to the "provider" object in ~/.config/opencode/opencode.jsonc,
// and set "model" to "bridge1/route1"
"bridge1": {
  "npm": "@ai-sdk/openai-compatible",
  "name": "Bridge1",
  "options": {
    "baseURL": "http://127.0.0.1:54321/v1",
    "apiKey": "YOUR-GATEWAY-KEY"
  },
  "models": {
    "route1": {
      "name": "route1",
      "attachment": true,
      "modalities": {
        "input": [
          "text",
          "image"
        ],
        "output": [
          "text"
        ]
      },
      "limit": {
        "context": 262144,
        "output": 32768
      }
    },
    "mtp-qwen3.6-35b-a3b-gguf": {
      "name": "mtp-qwen3.6-35b-a3b-gguf",
      "attachment": true,
      "modalities": {
        "input": [
          "text",
          "image"
        ],
        "output": [
          "text"
        ]
      },
      "limit": {
        "context": 262144,
        "output": 32768
      }
    }
  }
}

These OpenCode connection values use a placeholder key. Merge the complete provider entry from Gateway into your OpenCode configuration; keep its generated model and context fields.

Figure 4. OpenCode connection values. Replace YOUR-GATEWAY-KEY with your own gateway key; the base URL ends in /v1.

Connect your client

OpenCode setup

  1. Select this model in Bridge1. Merge Gateway’s generated bridge1 provider entry into your OpenCode configuration and select bridge1/route1 or its supplied plain model id.
  2. Keep attachment and modalities fields when supplied. Check compaction and prompt-reread limits in the OpenCode guide before a long chat.

Pi.dev setup

  1. Copy Gateway’s custom-provider JSON for the chosen model and verify the model selection before use.
  2. Keep input, contextWindow and maxTokens when supplied. Early support covers one short smoke-test turn; follow the Pi.dev guide for the current setup.

Codex setup

  1. Save Gateway’s generated provider configuration with wire_api set to responses and a base URL ending in /v1.
  2. Use route1 or the plain model id supplied by Gateway. For Codex Desktop, use the same configuration, then quit and reopen the app.

Hermes Agent setup

  1. Add a custom endpoint with Gateway’s URL, your non-blank key and route1 or the supplied plain model id. Use Test, then Save.
  2. Preserve generated vision and context values, including supports_vision when supplied. Early support covers a single smoke-test turn.

Claude Code setup

  1. Copy the Claude Code launch command from Gateway and run it in your project folder with your own gateway key.
  2. Keep claude-route1, timeout values and any extra context setting generated for the selected window. Use the guide to review Auto mode limits.

Claude Desktop setup

  1. Download config.json from Gateway, enable Developer Mode and open Configure Third-Party Inference; choose New → Import in the configurations switcher and select the file.
  2. Select the Bridge1 configuration, restart Claude Desktop and use Test connection. Review Code tab timeouts before a long prompt.

Limits

Check client support and known limits

Questions

Can I budget Bonsai 2 memory from its download size?

Use the estimated running memory at the admitted window and check the recorded measured depth, rather than budgeting from download size. Storage and running memory are different quantities. The reference result does not establish fit on a smaller Mac, and subtracting the download from the peak does not measure cache size.

Budget memory for your Mac

Does ternary compression establish Bonsai 2 coding quality?

No. Compression describes the weights. Publisher evaluations and Bridge1 memory measurements answer different questions, and no Bonsai 2 coding pass rate is published here. Try a small change with a test in your own project before planning a longer session.

Read coding evaluation conditions

Sources

  1. Prism ML Bonsai 2: Qwen3.8 base, ternary representation, Apache-2.0 · Accessed
  2. Earlier Prism ML Bonsai: Qwen3.6 base, Apache-2.0 · Accessed
  3. Bridge1 model catalog: profiles and reference Mac · Accessed
  4. Bridge1 coding evaluation: conditions and limits · Accessed

Make room for local coding

Check your Mac.
Choose your model.