Gemini CLI vs Gemma Tuner Multimodal

Gemini CLI brings Google's Gemini 2.5 Pro directly into your terminal as a local, open-source AI agent. Released under Apache 2.0, it operates in a ReAct (Reason + Act) loop — meaning it thinks, acts, observes results, and iterates until the task is done. It connects to local and remote MCP servers, supports a GEMINI.md system prompt file for project-specific context, and handles everything from coding to research to task management. The free tier is unusually generous: 60 model requests per minute and 1,000 requests per day at no cost with just a personal Google account. That's 1 million token context on Gemini 2.5 Pro, for free, at scale. For teams that have been paying for Claude Code or GitHub Copilot just to get terminal AI access, this changes the math significantly. Google open-sourced the tool in response to growing momentum from Claude Code and OpenAI's Codex CLI — but the free tier generosity is the real differentiator. Whether Google can maintain those quotas as usage scales is the open question, but the initial offering is hard to ignore.

Gemma Tuner Multimodal is an open-source fine-tuning toolkit for Google's Gemma 4 and Gemma 3n models that runs entirely on Apple Silicon using PyTorch with Metal Performance Shaders (MPS) backend — no NVIDIA GPU or cloud infrastructure required. It supports LoRA training on multimodal inputs: audio, images, and text simultaneously, using local CSV files or streamed from Google Cloud Storage or BigQuery. The tool targets the growing segment of developers who own M-series Macs but have been locked out of fine-tuning workflows that assume CUDA availability. Gemma 4's architecture is particularly well-suited to this use case: its 4B multimodal variant (designed for on-device deployment) trains efficiently on M3 Max and M4 Pro hardware within the available unified memory constraints. Primary use cases include medical transcription fine-tuning (audio → text with clinical terminology), visual QA systems (image + text → structured response), and private on-device pipelines where cloud API calls are prohibited by compliance requirements. The project fills a specific niche that Google's own fine-tuning documentation doesn't cover well for Apple hardware.