Ollama release notes April 2026: the boundary v0.21.0 does not move

v0.21.0, published on April 17, 2026. The headline additions are three integrations inside `ollama launch` (Hermes, GitHub Copilot CLI, and OpenClaw multi-channel) plus a GPU change (flash attention enabled for Gemma 4 on compatible hardware). The headline fixes are the Gemma 4 nothink renderer restored with the e2b-style prompt, a Gemma 4 Metal compiler error resolved, macOS cross-compiles no longer triggering `generate` during cmake, and `ollama launch` no longer rewriting config files when nothing changed. Everything in the release notes is either a new inbound integration, a model-layer quality improvement, or a developer-ergonomics fix.

No. None of the additions in v0.21.0 touch Mac-desktop action. OpenClaw routes messages from WhatsApp, Telegram, and Discord into the local model's context; that is an input channel over stdio and HTTP, not a GUI action layer. The Copilot CLI integration lets a coding CLI consume the local model; that is a stdin/stdout surface, not a desktop automation surface. Ollama's boundary stops at text tokens in and text tokens out (plus tool-call JSON for models that support tool use). Everything above that boundary, including every pixel and every CGEvent on a Mac screen, lives outside the scope Ollama ships.

In Fazm's case it lives in a 21 MB ARM64 Mach-O at Fazm.app/Contents/MacOS/mcp-server-macos-use. The ACP bridge (Node process) registers it as a local MCP server. The registration block is in acp-bridge/src/index.ts at lines 1057 to 1064: a single `existsSync(macosUseBinary)` guard, then `servers.push({ name: "macos-use", command: macosUseBinary, args: [], env: [] })`. Zero provider-specific arguments. Zero Anthropic-specific environment variables. The binary speaks MCP over stdio and exposes six tools, all suffixed `_and_traverse`, that walk the frontmost app's accessibility tree via `AXUIElementCreateApplication(pid)` and return the re-walked tree in the same response as the action result.

At the code level, it is a single-line swap: `DEFAULT_MODEL` at acp-bridge/src/index.ts line 1245 points at `claude-sonnet-4-6` today, alongside `SONNET_MODEL` on line 1246. The deeper lift is an inference-loop adapter that speaks Ollama's OpenAI-compatible `POST /v1/chat/completions` on `http://localhost:11434` instead of Anthropic's `POST /v1/messages`, and translates the tool-call JSON shape between the two. That adapter would sit where `ClaudeAcpAgent` sits in the ACP SDK today. The perception and action primitives, the `mcp-server-macos-use` binary and its six `_and_traverse` tools, would not need to change at all, because they were registered with `args: []` and `env: []` on purpose.

The macOS cross-compile fix (cmake builds no longer triggering `generate` on some Xcode versions) and the Gemma 4 Metal compiler fix are the two changes that directly affect the Apple Silicon install path. The Gemma 4 flash attention switch on compatible GPUs is mostly a Linux/NVIDIA win in practice, because Apple Silicon's unified memory architecture runs Gemma 4 through Metal Performance Shaders rather than through the flash-attention CUDA kernel. The Copilot CLI and OpenClaw additions are cross-platform. If you are on a Mac, the first two fixes are what quietly unbroke your local `ollama run gemma4` if it regressed earlier in April.

The direction of travel is consistent: Ollama is expanding horizontally into adjacent runtimes and channels rather than vertically into the application layer. 2025 added the OpenAI-compatible REST surface on `localhost:11434`, Modelfile improvements, and GGUF coverage across Llama, DeepSeek-R1, Qwen, Kimi, gpt-oss, and Gemma. 2026 so far has added `ollama launch` as a one-command config, multi-channel (OpenClaw), and coding-agent integrations (Copilot CLI, Hermes). That scope is deliberate: the project is the model-runtime layer, and it stays there even as its integration surface grows.

The interesting trigger is not a specific version number, it is a shape change: if Ollama exposes an Anthropic-compatible /v1/messages endpoint in addition to the OpenAI-compatible /v1/chat/completions endpoint, then the ACP SDK Fazm wraps today would become a drop-in client for local Ollama models with no adapter work. Until then, the boundary where a future Fazm release would integrate is the ACP SDK, not the MCP server. The MCP server is already provider-agnostic because its registration at acp-bridge/src/index.ts lines 1057-1064 never contained a provider-specific flag in the first place.

One line per element. Each line carries the AX role, the accessible title, the CGFloat frame, and a visibility flag. A real line from a Fazm Dev window looks like: `[AXButton (button)] "Send" x:6272 y:-1754 w:56 h:28 visible`. A full window traversal is about 441 elements and completes in roughly 0.72 seconds. The model substring-searches for the word it wants (`Send`, `Reply`, `Compose`), reads the x/y/w/h off the same line, and passes those values as the arguments to the next `_and_traverse` tool call. Nothing about that format depends on the model being Claude. A Gemma 4 or Llama 3.1 instruct model running on Ollama would read the same text.

Two layers. A perception layer, which turns what is on the screen into tokens the model can reason over, and an action layer, which translates the model's tool-call JSON back into real CGEvent mouse/keyboard events. Fazm ships both as the `mcp-server-macos-use` binary: perception is the AX tree walk (kAXRole, kAXTitle, kAXFrame), action is CGEvent click, type, and scroll. Those primitives are what a Mac agent needs regardless of whether the model was served by Anthropic, OpenAI, Google, or a local Ollama endpoint. Ollama's release notes, by design, never include a layer above the token boundary.

All three anchor points are in one file: acp-bridge/src/index.ts inside the Fazm desktop source tree. Line 63 resolves `macosUseBinary` to `Fazm.app/Contents/MacOS/mcp-server-macos-use`. Lines 1057 through 1064 are the `existsSync` guard plus the `servers.push({ name: "macos-use", command: macosUseBinary, args: [], env: [] })` registration. Line 1245 declares `DEFAULT_MODEL = "claude-sonnet-4-6"` and line 1246 aliases it as `SONNET_MODEL`. Line 1266 is the `BUILTIN_MCP_NAMES` set, which contains exactly five entries: `fazm_tools`, `playwright`, `macos-use`, `whatsapp`, `google-workspace`. For end-user verification, right-click Fazm.app, Show Package Contents, open Contents/MacOS, and run `file mcp-server-macos-use`; it reports `Mach-O 64-bit executable arm64`.