Story
I ran Gemma 4 as a local model in Codex CLI
1 report
1 website
1 discussion
Latest report
Overview
Gemma 4 was tested as a local model in Codex CLI to determine its viability as a replacement for cloud models in coding tasks. The testing involved using a 24 GB M4 Pro MacBook Pro to evaluate Gemma 4's local tool calling capabilities.
Summary from blog.danielvaughan.com.
Reports
One report so far. Additional coverage will appear here when it is linked to this story.
blog.danielvaughan.com
I ran Gemma 4 as a local model in Codex CLI
Read report →
Community reactions
Each reaction summarizes sampled comments from the linked discussion.
Hacker News · blog.danielvaughan.com
Historical count: 5 · 5 saved in sample · Historical sample
Analysis ready
Read this discussion’s reaction
Based on 5 sampled comments from this thread. Analyzed 2026-04-13.
- Praise: Running Gemma 4 on local hardware like the M3 Ultra demonstrates the model's capability to handle large context sizes effectively, which is crucial for complex tasks.
- Praise: The integration of Gemma 4 with tools like Zed via ACP showcases its versatility and ease of use in real-world applications.
- Praise: Users report significant performance improvements with the M5 Pro, indicating that hardware upgrades can lead to enhanced model efficiency and speed.
- Praise: The ability to offload MoE tasks to the CPU allows for flexibility in managing context size and token generation speed, which can optimize performance.
- Concern: Concerns about the quality of fine-tuned models compared to original versions suggest skepticism about performance claims, highlighting the need for thorough benchmarking.
- Concern: Issues with tool calling in models like Qwen 3.5 indicate that practical challenges remain, which can hinder user experience and effectiveness in coding tasks.
- Concern: The necessity of increasing context size to achieve useful results points to potential limitations in the model's default configurations, which may not meet all user needs.