WebSearchToolCall incorrectly requires an action on every returned item

Open Beginner friendly

#572 opened on Sep 6, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 2/5
Estimated time: 1-3 hours
Newbie friendliness: 78/100

Issue type: Bug
Clarity: Clearly specified
Activity status: Active
Tech stack: openapi
Domain: api

Research direction

Start in openapi.yaml near line 67210, reviewing the WebSearchToolCall.action schema and the linked source reports. Reconcile the schema with completed web_search_call objects where action is omitted, and separately verify the intended JSON-null behavior without relying on Python None; done means the published schema reflects both decisions.

Written by the indexing model from the issue text.

Description

bug specification

Source reports

https://github.com/openai/openai-python/issues/3179

Current specification gap

Affected surface: POST /responses; WebSearchToolCall.action.

The Python report observes completed web_search_call objects with action=None. That SDK representation alone does not distinguish omission from JSON null. The current public schema requires action on every item. Please reconcile requiredness with completed items whose action is absent, and verify JSON-null behavior separately.

Specification reviewed at b61ced9.

Expected reconciliation

Make action optional where the API omits it. Determine JSON-null behavior separately; do not infer it solely from a Python None representation.

Verification scope

Reviewed the source reports, relevant comments, and current published schema. No new live API request was made. This mirrors the specification gap and preserves the original reproduction; it does not claim that a fix has shipped.

Dominant language: No language data
Stars: 2.5k
Forks: 527
Avg merge: 1h 46m
Merged PRs (30d): 2

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[Bug]: Matrix progress drafts fail with "Matrix runtime not initialized" during tool activity Open

bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

openclaw/openclaw#155298 · 2 comments · 1 reaction · Opened Sep 22, 2026
[Bug] NULL pointer dereference in llm_running_callback (NGZA-AX-LLM #3) Open

Difficulty 1/5 Under an hour Newbie friendliness 90/100

AXERA-TECH/ax-llm#77 · Opened Sep 22, 2026
resume() sends a second HTTP response (400) after a successful resume Open

Difficulty 1/5 Under an hour Newbie friendliness 90/100

games-on-whales/wolf#509 · Opened Sep 21, 2026
MCP client has no httpx timeout, so the event stream fails after 5 seconds Open

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

Azure/azure-functions-agents-runtime#228 · Opened Sep 21, 2026
feat(mcp): friendlier error when `run_cloud_sync` is called on a disabled connection Open

enhancement

Difficulty 2/5 1-3 hours Newbie friendliness 72/100

airbytehq/PyAirbyte#1205 · Opened Sep 21, 2026

More Backend & API Design issues