openai / openai/openai-openapi

Image generation call replay incorrectly requires result and status

Open
#575 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Source reports

Current specification gap

Affected surface: POST /responses input; ImageGenToolCall via Item.

The source reports that the documented image-ID multi-turn example works while request typing requires result and status. The current public ImageGenToolCall requires both fields and reuses that component in input. This is distinct from assistant-message content issues #475 and #565.

Specification reviewed at b61ced9.

Minimal shape

{
  "type": "image_generation_call",
  "id": "ig_example"
}

This is a sanitized illustration of the reported shape, not a new live API capture.

Expected reconciliation

Model input replay separately from generated output as needed so an image ID can be reused without invented result/status values.

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.

Contributor guide

Open the contributing guide

First steps

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

Research direction

Start in openapi.yaml around line 42240 and compare the ImageGenToolCall component with its use for POST /responses input. Review the linked source report and comments, then separate input replay from generated output so the minimal type-and-id shape is accepted without result or status; preserve those fields where output requires them.

Written by the indexing model from the issue text.

Assessment

Tech stack
openapi
Domain
api
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.