Writing

Tutorials · October 25, 2026

How to Run Qwen3.5 Local Coding on M1 MacBook

Learn how to set up Qwen3.5 local coding on M1 MacBook for student assignments without cloud APIs using a 16GB machine and quantized models.

If you teach computer science or mentor students who need help with programming assignments, relying on cloud APIs introduces privacy concerns, recurring costs, and internet dependency. Running an AI model directly on your hardware solves these problems. This tutorial covers Qwen3.5 local coding on M1 MacBook setups specifically for educators and students working with 16GB of RAM. Recent discussions on r/LocalLLaMA highlight that older Apple Silicon machines, like the 2021 M1 Pro MacBook with 16GB of memory, can handle capable coding models when configured correctly. Community members are actively testing inference engines optimized for Apple Silicon to run Qwen and Nemotron models locally. However, before you begin, there is an important detail regarding model availability.

A MacBook terminal window showing a model download command

What you need

  • A MacBook with an M1 chip (M1, M1 Pro, M1 Max, or M1 Ultra) and 16GB of unified memory.
  • macOS updated to a version supported by Ollama.
  • An active internet connection for the initial download of the software and model weights.
  • Terminal access on your Mac.
  • Basic familiarity with command-line interfaces.

According to the Ollama Documentation, Ollama natively supports Apple Silicon M1 chips and allows you to pull and run Qwen model variants locally via the command line interface without relying on cloud APIs. The documentation explicitly notes that users with 16GB of RAM should select a quantized model size that fits within available memory, such as 8B or smaller.

A critical note from the Ollama Documentation: As of mid-2025, the latest official release is Qwen3. The specific version "Qwen3.5" does not yet exist as an official model version. When setting up Qwen3.5 local coding on M1 MacBook environments, you will actually be pulling the latest available Qwen3 quantized variants (such as the 4B or 8B sizes) until a newer official release is published. The steps below use the currently documented Qwen3 library, which serves as the functional foundation for this workflow.

A student working at a desk with a closed laptop

How to Qwen3.5 local coding on M1 MacBook

Follow these steps based on the Ollama Documentation to install the runtime, download a memory-appropriate model, and interact with it locally.

  1. Download and install Ollama. Navigate to the official Ollama website and download the macOS installer. The Ollama Documentation confirms that the software natively supports Apple Silicon M1 architecture. Open the downloaded file and follow the system prompts to move the application to your Applications folder.
  1. Open Terminal. Launch the Terminal application on your Mac. You will use the command line to manage models and send prompts. Ollama runs as a background service once installed, so you do not need to manually start a server process.
  1. Select a quantized model appropriate for 16GB RAM. The Ollama Documentation advises users with 16GB of RAM to choose a quantized model size that fits within available memory, recommending 8B or smaller. In the r/LocalLLaMA thread discussing benchmarks for M1 Pro 16GB machines, users tested Qwen 4B and 9B Q4 (4-bit quantized) models. For a 16GB machine handling both the operating system overhead and the model, a 4B or 8B parameter model is the safest choice to prevent memory swapping.
  1. Pull the model. In your Terminal, type the command to pull your chosen model from the Ollama library. For example, to pull a standard Qwen3 model, you would enter ollama run qwen3. The Ollama Documentation details pulling Qwen3 model variants directly via the CLI. The system will download the model weights to your local drive. Wait for the download to complete.
  1. Run the model locally. Once the download finishes, the ollama run command drops you into an interactive chat session directly in the Terminal. All processing happens on your M1 chip. No data is sent to external cloud APIs. You can now input coding questions or assignment prompts.
  1. Exit the session. When you are finished, check the official Ollama help documentation for the supported command to exit the interactive prompt. The model remains downloaded on your machine for future use.

If you are exploring specialized inference engines mentioned in the r/LocalLLaMA discussion, such as Kapitsa, confirm the installation controls and required commands in that project's official GitHub repository rather than assuming they match Ollama's setup.

Where this goes wrong

The most common failure point when attempting Qwen3.5 local coding on M1 MacBook setups is exceeding the 16GB memory limit. Always adhere to the Ollama Documentation guidance to use 8B or smaller models for 16GB configurations. While the r/LocalLLaMA thread mentions benchmarking a 35B model on an M1 Pro 16GB machine, the sources do not document specific causal failure outcomes for loading larger models.

Finally, remember the versioning constraint. Because Qwen3.5 is not yet an official release according to the Ollama Documentation, searching for that exact tag will result in an error. Use the latest Qwen3 tags available in the library.

Worked Example: Generating a Python Quiz

Here is a practical classroom example you can copy into your Terminal after completing the steps above. This demonstrates how to use the local model to generate educational content without sending student data to the cloud.

ollama run qwen3
>>> Write a short Python function that calculates the factorial of a number. Then, provide three multiple-choice quiz questions about how the code works, including the correct answers.

The model will stream the Python code and the quiz questions directly in your Terminal. Because it runs locally on your M1 chip, you can safely use this during exams or in classrooms where internet access is restricted or monitored. If the output stops prematurely, check your available system memory in Activity Monitor to ensure the model has enough headroom to finish generation.

Sources