Anton Panasenko 77b0c75267 feat: search_tool migrate to bring you own tool of Responses API (#14274) ...

## Why

to support a new bring your own search tool in Responses
API(https://developers.openai.com/api/docs/guides/tools-tool-search#client-executed-tool-search)
we migrating our bm25 search tool to use official way to execute search
on client and communicate additional tools to the model.

## What
- replace the legacy `search_tool_bm25` flow with client-executed
`tool_search`
- add protocol, SSE, history, and normalization support for
`tool_search_call` and `tool_search_output`
- return namespaced Codex Apps search results and wire namespaced
follow-up tool calls back into MCP dispatch

77b0c75267 · 2026-03-11 17:51:51 -07:00

History

..

schema

feat: search_tool migrate to bring you own tool of Responses API (#14274)

2026-03-11 17:51:51 -07:00

src

chore(app-server): stop emitting codex/event/ notifications (#14392)

2026-03-12 00:45:20 +00:00

tests

Stabilize protocol schema fixture generation (#13886)

2026-03-09 13:51:50 -07:00

BUILD.bazel

feat: vendor app-server protocol schema fixtures (#10371)

2026-02-01 23:38:43 -08:00

Cargo.toml

feat(app-server): support mcp elicitations in v2 api (#13425)

2026-03-05 07:20:20 -08:00