CLIENT SUPPORT
Compatibility
Support is qualified by protocol, model capability, and actual client behavior.
| Surface | Current implementation | Staging availability |
|---|---|---|
| Chat Completions | Text and function-tool conversations, including streaming | Gemini 3.8 Flash |
| Streaming | Incremental Chat, Responses, and Messages events | Gemini 3.8 Flash |
| Responses / Codex CLI | Text, function and namespace tools, encrypted continuations | Real Codex CLI file-read/edit tasks passed |
| Messages / Claude Code | Text, tools and signed thinking continuations | Real Claude Code file-read/edit task passed |
| Cursor / Hermes | Planned after the first MVP | Unqualified |
Chat Completions supports n: 1, store: false, and the default service tier. Unsupported fields or model capabilities fail before financial admission. Yugos does not execute your tools.
Streaming headers show pending billing. Check the request receipt for the final charge. An interrupted stream can leave usage or cost pending; it is never reported as a free request. To receive final token usage, set stream_options: { include_usage: true } for Chat Completions. Responses and Messages return their native usage events.
Messages supports text, tools, cache markers, and signed thinking continuations. Keep thinking signatures and tool results for later turns. Tools run in your client. Token counting and hosted tools are outside the first MVP; Claude Code uses estimated context counts.
Responses supports text, function/namespace tools and stateless reasoning continuations with store: false. Keep returned input items for the next turn. A reasoning continuation stays with its original model. Saved conversations and hosted tools are outside the first MVP.
Start with the tested Codex CLI or Claude Code configuration. These bounded staging tasks use actual Gemini calls and finalized usage receipts. Images, hosted tools, saved conversations and custom-tool payloads are outside the Gemini launch qualification.