Make Codex and Claude Code subscriptions go further: a local model router that gives routine agent work to economical models and keeps your strongest model for the hard parts.
Code map
Start with the user action below, follow its production owner, then read one representative scenario. This map locates current code and contracts; requirements belong in specifications, implementation detail beside the code, and validation results in the relevant run record.
Read progressively
- Find the capability below, or search with
rg -n -i '<user action, symptom or domain term>' docs/code-map/. - Once the relevant topic is located, prefer reading its complete code-map page, including ownership boundaries and cross-references. The search match locates the page; its surrounding context helps interpret the entry.
- Follow the production owner and a representative scenario, then expand into linked code, specifications or local guides as needed. Unrelated map pages need not be read by default.
Find a capability
Read across boundaries
| Map | Scope |
|---|---|
| Architecture and ownership | Shared layers, source admission, durable state, observation and change boundaries |
| Agent integrations and Workers | Shared configuration/lifecycle owners, with Codex, Claude, Qoder, Pi, DSH and OpenCode differences together |
| Decision models and routing | Saved connections, provider adapters, per-turn policy and competence attribution |
| Tests as product documentation | Proof levels, reusable fixtures, representative fault cases and validation selection |
Keep new navigation organized by stable responsibility, not by a provider or a completed feature. Add an ecosystem to the shared comparison and link its native leaf. Put detailed protocol rules in their canonical contract and operating steps in the existing local guide. When an owner moves, update its entry and incoming links instead of appending another implementation note to this index. Keep each matched entry a short clue about where to look next and why. Detailed rules, parameter lists, exhaustive exceptions and validation history belong in the linked specification, local guide or run record.