Show activity for standalone web search calls#24693
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f8b642836c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
c1cb3be to
bab1e7d
Compare
|
@codex review this |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: bab1e7d324
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
e0ef3b6 to
ad2852d
Compare
Why
Standalone
web.runcalls run in the extension, so they need normal web-search progress activity while a request is in flight and durable completed activity after a thread is reloaded.Follow-up to #23823; uses the extension turn-item emission path added in #24813.
What changed
web.runstart/completion items through the host turn-item emitter, preserving standard client delivery and rollout persistence.open/findcommands.Searched the weborSearched the web for <detail>, with snapshot coverage for the detail-free case.thread/readafter a fresh-process reload.Testing
just test -p codex-web-search-extensionjust test -p codex-app-server -E "test(standalone_web_search_round_trips_encrypted_output)"