Dev open-sources TITAN: a repo-native Codex methodology pairing SOL planning with LUNA implementation

sokobih · reddit · 2026-09-14

A heavy Codex user distilled his multi-session development experience into an open-source methodology called TITAN (Technical Intelligence, Tasking & AI Navigation), built around the idea that the repository itself carries the development workflow.

His key observation: SOL and LUNA are not interchangeable. SOL excels at tasks requiring thinking — architecture, business rules, debugging, planning — while LUNA works surprisingly well once the thinking is done. The flow: SOL decides what to build and writes a detailed implementation plan → switch to LUNA to implement → tests → STOP/review → next task. Making SOL write plans explicitly prevents LUNA (or weaker models) from making architectural decisions during implementation.

To fix decisions scattered across sessions in longer projects, he moves that context into the repo:

Two rules stand out: the STOP rule — if LUNA hits a codebase/plan mismatch while implementing, it stops and reports rather than redesigning, and the user switches back to SOL; and plan timing — no massive upfront plans; detailed plans are generated just before a module is built, after SOL inspects current repo state. ASTRA serves as an optional critical reviewer for expensive decisions rather than a permanent agent, and UI tasks are separated from backend work since visual tasks fail for different reasons.

He notes TITAN is overkill for small projects but suits long-lived apps with real business rules, permissions, and state transitions. It's packaged as an open-source starter on npm: run npx -y u/netelite/titan@latest in an empty project, open it in Codex, select SOL, and prompt "Start this project using the TITAN methodology".

Related event: Dev open-sources TITAN, a repo-native methodology for Codex(2 posts)→

Original post →

More from coding & agent

coding & agent channel →