Client tool compatibility

Check the matrix for the tool types and protocol your client uses.

Responses-native models

No Responses-native models are currently available.

Tool type compatibility matrix

Tool typeWhen routed to a Responses-native routeOtherwise
functionSupportedSupported
custom (e.g. Codex exec)SupportedAdapted (Gemini routes pending)
local_shellSupportedAdapted
namespace (tool groups)Supported (flattened)Same
tool_search · execution:"client"SupportedAdapted for OpenAI/Anthropic protocols (Gemini unverified)
tool_search · server-side searchSupportedNot supported: 400 with reason=server_executed
shell (local) / apply_patchSupportedReturns 400 with reason=not_adapted
computer / computer_use_previewSupportedPlanned (needs multimodal tool output)
mcp / web_search / file_search / code_interpreter / image_generationSupportedNot supported: 400 with reason=server_executed

Status reflects the current production release and is updated on deploy; rejected requests state the reason and available alternatives in the error message.

Anthropic output and thinking controls

For Messages requests routed to an Anthropic upstream, see the Anthropic field reference for the supported output_config and thinking shapes.

See current Responses-native models · Find error codes