diff options
| author | t <t@tjp.lol> | 2026-06-13 23:45:59 -0600 |
|---|---|---|
| committer | t <t@tjp.lol> | 2026-06-15 15:08:32 -0600 |
| commit | 02b4c7a35ac0b714bc045d54fb4bb45d1ce4e490 (patch) | |
| tree | 134196a82dd6fdd55b735be4c0cf38428c85038d /docs | |
| parent | 71643a5d69ffc40882c9fcde3cc8a3bcf02d7396 (diff) | |
Add Codex Responses support and session debugging
Teach provider config and auth resolution about the Codex Responses
dialect, including user-facing `style = "openai_responses"` with
`dialect = "codex"`. Serialize and parse Responses traffic with
provider-specific reasoning replay, assistant phase metadata, and robust
function-call assembly keyed by `output_index` so streamed tool inputs
survive proxy quirks and empty terminal payloads.
Also persist thinking origins and message metadata across sessions, add
the Anthropic interleaved-thinking header switch, write per-session
debug logs, and improve the TUI and scripts for inspecting tool output
and session costs.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/oauth-provider-auth.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/oauth-provider-auth.md b/docs/oauth-provider-auth.md index 96312e1..268c7e9 100644 --- a/docs/oauth-provider-auth.md +++ b/docs/oauth-provider-auth.md @@ -573,9 +573,9 @@ it is the OpenAI **Responses API** at items, `reasoning`, `include: ["reasoning.encrypted_content"]`, `store: false`; headers `Authorization: Bearer`, `chatgpt-account-id`, `OpenAI-Beta: responses=experimental`, `originator: codex_cli_rs`). That is a -new wire dialect, implemented as the **`openai_responses` provider style** -(`provider_openai_responses.zig` + `openai_responses_json.zig`), distinct from -`openai_chat`. The default config ships a commented `[providers.codex]` / +Responses-family dialect: configure it as `style = "openai_responses"` with +`dialect = "codex"`, which maps to the internal `openai_codex_responses` +`APIStyle`. The default config ships a commented `[providers.codex]` / `[auth.openai_codex]` example. The serializer maps system→`instructions`, user/assistant text→message items, tool calls→`function_call` / `function_call_output` items, and tools→flat function entries; the stream |