# Example manifest: opencode

## Metadata

| Field | Value |
|---|---|
| Institute | Molodetz Institute — Research & Retrieval Division |
| Subject | cap-protocol |
| Document type | Source Dossier |
| Tier | 1 |
| Source title | CAP agent manifest for opencode |
| Source URL | https://github.com/rsclaw-ai/cap-protocol/blob/main/examples/opencode.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 (52 lines) |
| Confidence | High |
| Status | Active |

## Summary

PTY-shape manifest for opencode with `❯`/`›` idle alternatives and `^Error:` error lines; notably `ask_user` all-false except free_text, and no model_arg.

## Key findings

- No `model_arg`: drivers must cope with agents that accept no model flag (config `model` then has nowhere to go; warn, not fail).
- Idle alternatives (`❯`, `›`) show the idle list is OR-matched across glyphs, matching multiple TUI states.
- Like codex, lags STATUS.md, which routes opencode over ACP in practice.

## Pros / strengths

- Pins the no-model-arg and multi-glyph-idle cases tai's driver must handle.

## Cons / limitations / caveats

- Stale relative to the implementation (ACP is the real opencode path).

## Relevance to tai

Parser/driver fixture for the no-model-arg case and multi-pattern idle matching.

## Changelog

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