# Example manifest: codex

## Metadata

| Field | Value |
|---|---|
| Institute | Molodetz Institute — Research & Retrieval Division |
| Subject | cap-protocol |
| Document type | Source Dossier |
| Tier | 1 |
| Source title | CAP agent manifest for codex |
| Source URL | https://github.com/rsclaw-ai/cap-protocol/blob/main/examples/codex.toml |
| Source type | example config |
| Source date (published) | Unknown, not stated (repo living file) |
| Date researched | 2026-10-18 |
| Researched by | tai (agent), model: Muse Spark, on behalf of retoor |
| Research method | direct raw-file fetch, read in full (51 lines) |
| Confidence | High |
| Status | Active |

## Summary

PTY-first manifest for codex: all fast-paths false, `›` idle glyph, `✗` error prefix, 120s init timeout, metered cost.

## Key findings

- Shows the all-false fast-path form explicitly rather than omitting the section; tai's parser must treat false and absent identically.
- The `›` (U+203A) prompt glyph is the live-captured turn-boundary marker the STATUS doc references.
- `init_timeout_seconds = 120` doubles the claude value: slow-booting TUI agents need per-manifest patience.

## Pros / strengths

- Minimal-but-valid shape that pins down which fields a PTY-only agent can omit.

## Cons / limitations / caveats

- Contradicts STATUS.md, which says codex defaults to stream-json; the example file lags the implementation.

## Relevance to tai

Second parser fixture (the sparse PTY-only shape) and the binding-preference test case (all false means PTY).

## Changelog

| Date | Change |
|---|---|
| 2026-10-18 | Initial dossier created. |