I’ve been using Claude Code daily for over a year. This is the personal project I now write all my code with — decided to share it. arc A while back I measured something that bothered me: two of my long Claude Code sessions (60h and 53h) degraded badly — and both were exactly the ones that hit context compaction twice. A 4.6h session that never compacted stayed sharp the whole way. The model wasn’t getting lazy. It was forgetting . So I built Arc — a terminal app where Claude and Codex work as a team, and neither one is the memory : Claude interviews you, asks the questio, and plans Codex writes the code in isolated worktrees — never in your checkout a different Claude reviews it (never thsks before it’s even allowed to see thediff) your project’s actual tests run , and nothout evidence on disk every goal, decision, plan, and proof lives in SQLite — kill -9 it mid-build, resume, nothing is lost demo It runs on the Max/Plus subscriptions you already pay for — no API keys, no per-token billing. The moment that sold me on my own tool: I pointed Arc at its own repository. Its scouts fact-checked my task descriptions against the real code and refuted my wrong assumptions five times — correctly, every time . Itsintegration reviewer blocked a design contradiction I’d missed. It shipped its own last six features. Agents that can’t lie about being done, reviewing agents that can’t grade their own homework. pipeline Honest fine print: it’s alpha, macOS-first (Linux degrades gracefully), MIT licensed, 4 runtime dependencies, ~330tests that run against fake CLIs so CI spends zero tokens. If “models think, the program remembers” sounds like something you’ve needed, a ⭐ genuinely helps: https://github.com/Zie619/Arc Happy to answer anything about the architecture — especially the part where the reviewer is kept blind, and what running an orchestrator on itself taught me. submitted by /u/eliadkid
Originally posted by u/eliadkid on r/ClaudeCode