Dan Kornas (@DanKornas) open-sourced MIT repo-harness: a file-backed workflow harness for Claude Code and Codex that writes plans, contracts, checks, handoffs, and review evidence into the repo, with Plan→Contract→Review lifecycle, typed hook runtime, progressive context loading, and CodeGraph — so the next session continues from project files instead of chat memory.

Key Takeaways

  • ✓Ship: MIT open-source repo-harness for Claude Code / Codex.
  • ✓Mechanism: plans/contracts/checks/handoffs in-repo; Plan→Contract→Review.
  • ✓Value: resume from project files instead of fragile chat memory.
⚡

Key Decision Metrics at a Glance

TL;DR Verdict
🏆 Benchmark RankRank
No model benchmark in this story · see current rankings
Full Leaderboard→
💰 Cost & PlansCompare
API & Subscription
Compare Plans↗
🛠️ Ecosystem & IDERules
Claude Code (Anthropic)
Setup IDE Rules↗
🧭

Heavy Claude Code use: compare subscription limits and API bills

Compare 40 dev plans & simulate token costs vs $20/mo subscriptions

⚔️ Compare Model→💰 Compare plans & limits↗
Action HubReady to adopt this in production?

Benchmark side-by-side against alternatives, or calculate monthly token cost vs subscription break-even.

⚔️ Launch VS Compare→💳 View Plans↗
Up NextCodeGraph: local code knowledge graph via MCP for Claude Code, Codex, and peers
Read Now→