Engineering references
These are technical design and verification records for contributors. For everyday use, start with the beginner guide and mode guides. A design record can contain proposals or old instructions; it is not a step-by-step user tutorial.
The user guides describe the current documented behavior. The repository also retains original design specifications, upstream navigation notes, fixtures, and dated verification records.
These engineering files are available on GitHub and are intentionally separate from the published user-guide navigation. A proposal, checklist, or dated instruction is not proof that a feature is currently shipped or supported on every platform.
Start with current acceptance
| Reference | Use it for |
|---|---|
| Dogfood acceptance | October 30, 2026 integration evidence, checked behaviors, and remaining limitations. |
| App agent guide | Backend routing, frontend boundaries, invariants, and validation rules. |
| Codebase map | Task-oriented source navigation. |
| UI preview harness | Credential-free fixture controls and screenshot recipes. |
| App-server events | Event and integration notes. |
Feature design records
| Area | Original reference |
|---|---|
| Provider registry and engine-neutral core | M1-C |
| pi runtime and policy gate | M1-D1, M1-D2 |
| MCP connectors | M1-E |
| Computer use | M3 and its follow-up records |
| Chat | M4-D |
| Work | M4-F |
| Checkpoints | M4-B |
| Native browser | M7 |
| Chain of Command | M9 |
| Complete specification archive | docs/specs |
Older records can contain local development paths, superseded options, and original implementation instructions. Prefer the live source, current guides, and more recent acceptance evidence when they disagree.
Protocol and support crates
- Protocol package: generated Codex app-server types pinned to 0.164.0.
- MCP proxy: proxy and code-intelligence support.
- Diagnostics MCP reader: standalone journal inspection.
- Fixtures: bounded test examples and redaction inputs.
Working with upstream
taucode is derived from CodexMonitor. The upstream sync runbook records the inherited multi-agent/config synchronization workflow. Account/login assumptions and experimental feature defaults in upstream documents may differ from taucode's own provider registry and profiles.
Use development and architecture for the current contribution path. Preserve upstream copyright notices and distinguish imported design decisions from verified taucode behavior.