Gemma 4 Multimodal Fine-Tuner vs oh-my-codex (OMX)

Gemma 4 Multimodal Fine-Tuner is an open-source toolkit that lets developers fine-tune Google's Gemma 4 and 3n models across all three modalities — text, images, and audio — using only Apple Silicon hardware. It runs natively on PyTorch with Metal Performance Shaders (MPS), bypassing the NVIDIA requirement that has historically blocked Mac users from serious local fine-tuning work. The toolkit handles the full training pipeline including dataset prep, LoRA adapters, and multi-modal data collation. It ships with working example notebooks, a validation suite, and clean abstractions that don't require deep familiarity with the underlying MPS stack. Apple Silicon's unified memory architecture actually helps here — large multimodal batches fit in memory that would otherwise require GPU VRAM splitting on CUDA setups. Posted to Hacker News on April 7 as a Show HN, it pulled 109 upvotes and 165 GitHub stars within hours. The timing is sharp: Gemma 4 just dropped days ago with new multimodal capabilities, and the community immediately wanted local fine-tuning. This fills that gap faster than Google's own tooling.

oh-my-codex (OMX) is an open-source orchestration layer for OpenAI's Codex CLI, created by Yeachan-Heo. The framing is dead simple: like oh-my-zsh extended the terminal, OMX extends Codex CLI with structured multi-agent workflows, customizable hooks, persistent memory, and a heads-up display (HUD) for monitoring agent activity. It hit 2,867 GitHub stars within days of going trending in early April 2026. OMX's key innovation is team-based execution: rather than one AI agent working through a task linearly, OMX spawns specialist roles — planner, implementer, reviewer, tester — each running in an isolated git worktree to prevent conflicts. The $deep-interview workflow gathers context before starting, $ralplan creates a structured action plan, and $team coordinates the parallel execution. It also adds native Codex hook ownership with PreToolUse/PostToolUse guidance, and ships with Windows and tmux reliability improvements. The practical use case: you have a complex feature to build across multiple files, and you want Codex to plan it properly before touching any code, run specialists in parallel for different modules, and produce a PR-ready result. OMX is that layer. It's explicitly for power users who already live in the terminal and find vanilla Codex too unstructured for serious projects.