← All guides

Can a Four-Bit Local Model Actually Ship a Feature? Pi Says Yes

I made a video testing Pi, the minimal coding agent people have been raving about, with a local model. A four-bit model running on a laptop sounds like it should struggle to edit a real file, but in my test it added a working dark-mode toggle without help. Here is the gist, the s

I made a video testing Pi, the minimal coding agent people have been raving about, with a local model. A four-bit model running on a laptop sounds like it should struggle to edit a real file, but in my test it added a working dark-mode toggle without help. Here is the gist, the setup, and why the agent is the part that mattered.

Why Pi over a bigger agent

Pi is a minimal terminal coding agent with just four built-in tools. No MCP support, no sub-agents, no permission loops, no plan mode, no built-in todos, no background bash. On a cloud model that trimming barely matters, but on a local model it changes the outcome, because a smaller model has less room to absorb a heavy system prompt and long tool chains.

So Pi keeps the surface small and lets the model spend its limited attention on the actual code. The people pushing it lately include the creator of Redis and the CTO of Hugging Face, mostly for running local models offline.

The setup I used

I served the Qwen 3.6 27B four-bit model through llama.cpp on my Mac, on port 8081, and pointed Pi at it. llama.cpp is the local runtime that hosts the model, and Pi connects to it as a provider. If you already run models with Ollama or MLX-LM, Pi can use those instead, so you are not forced to change your stack.

Starting Qwen 3.6 27B locally and selecting it inside Pi is a short sequence, and the video walks through each step.

The result

The task was a working dark-mode toggle in a real HTML file, run on a four-bit Qwen. Four-bit means the model is quantised down for a smaller memory footprint, which is exactly the kind of model you run when you want local coding to fit on a normal machine. Even at four bits this is a dense 27B, and in the run the inference felt fast, not sluggish.

Pi wrote a plan, used CSS custom properties for theming and JavaScript to toggle the class, and saved the file. The toggle worked. That is the signal I care about: a compressed local model, a minimal agent, and a feature that actually works at the end.

Watch the full install and demo in the video above. The models.json config is linked in the description. For more local-AI setup guides, openclawdc.com has walkthroughs on running models on your own machine.

I specialize in helping teams wire up local coding agents that ship real features. Book a call at cloudyeti.io/meet.

Need OpenClaw fixed live?

Remote rescue sessions for gateway, auth, tunnel, VPS, and model access problems.

See Rescue Session

Read next

Local LLM Coding Setup on Windows + NVIDIA: The Guide Mac Tutorials Skip (July 2026)
A Windows-native path to a local coding agent on an NVIDIA GPU. No WSL, no Docker required. Runtime choice, verifying GPU offload actually engaged, MoE offload for 12-16GB cards, and wiring a coding agent to a local endpoint.
Qwen 3.5 27B on a Single RTX 3090 Beats 120B Models on $70K H200 Rigs (For Agent Coding)
Qwen 3.5 27B dense Q4 on a single RTX 3090 one-shots agent coding tasks that 120B MoE models on $70K H200 rigs fail. Benchmarks, setup, and OpenClaw install steps.
Can a Local Model Actually Run OpenClaw? Two Honest Tests
I made two videos on running OpenClaw with a local model for zero API cost, one before Qwen 3.5 and one after, and the answer flipped between them. The pitch is simple: no API bill. The catch has always been that the model was not good enough. Here is what changed.
Context Window Traps (July 2026): Why Your Local Agent Breaks After 10 Prompts
Ollama's default context is far below what an agent harness needs. The system prompt and tool schemas alone eat 15-20K tokens, so a 4-8K window silently truncates your tools. How to check it, set it, and budget the KV cache VRAM.