Atlarix vs OpenAI Codex — Local-First Approval vs Cloud Autonomy
OpenAI Codex is a Rust-based, open-source coding agent that runs tasks in a containerized sandbox and lands results — often as pull requests — with strong autonomy and zero-data-retention options. It's excellent infrastructure for delegated, cloud-run work. Atlarix is the open-weight frontier harness: local-first, any-model, with your approval before every write. The two optimize for different loops.
| Atlarix | OpenAI Codex | |
|---|---|---|
| Where it runs | Local desktop, on your machine | Cloud sandboxes (local via --oss) |
| Output model | In-loop edits, you approve each write | Autonomous run → diff / pull request |
| Models | Open-weight Core + any BYOK + local | OpenAI models (local Ollama via --oss) |
| Codebase retrieval | Blueprint + FTS5 grep — no embeddings | Agentic file access / grep |
| Approval before writes | ✅ hunk-level queue | Autonomous by default |
| Write sandbox | ✅ per-OS, network stays on | ✅ container (cloud) |
| Open-weight first | ✅ | Partial (--oss local models) |
| Surface | Desktop workstation, editor-agnostic | CLI / cloud |
What Codex is
Codex (rebuilt in Rust, Apache-2.0) is designed for agentic, often-autonomous work: it runs shell and edits inside a sandbox that can't touch the rest of your machine without approval, manages context with compaction, and is built for stateless, zero-retention operation. The `--oss` flag points it at a local Ollama model, and you can wire any OpenAI-compatible endpoint — but the harness is tuned around OpenAI's models and a delegate-then-review loop.
What Atlarix is
Atlarix keeps you in the loop and keeps the work local. Its Core models are the open-weight frontier labs (DeepSeek, Qwen, Kimi, MiniMax) via a live models.dev catalog, plus any BYOK provider or fully local Ollama / LM Studio. Retrieval is Blueprint + disk-backed FTS5 — structural and lexical, no embeddings. And every write surfaces a diff for hunk-level approval before it executes.
Autonomy vs. approval
Codex's bet is autonomy: hand off a self-contained task, let it run sandboxed, review the diff or PR afterward. That's powerful when the correct output is easy to judge from a diff. Atlarix's bet is that for non-trivial changes you want to see what changes and why before it lands — so the approval queue isn't a limitation, it's the workflow. Both ship real write sandboxes; Atlarix's runs locally per-OS and keeps the network on so installs and git still work.
When to use each
Use Codex for delegated, cloud-run tasks where autonomy and a PR-shaped output fit your team, and OpenAI models are your default. Use Atlarix when you want open-weight or local models first, no-embeddings retrieval, and to review every change on your own machine rather than after the fact.
Codex is an excellent autonomous, cloud-sandboxed task runner. Atlarix is a local-first, open-weight harness that keeps the developer in the loop. The right choice comes down to whether you want to review a finished diff or approve the work as it happens — and whose models you want to run.