Support for the new Prompts API (successor to deprecated Assistants API)

Hi,

OpenAI has officially deprecated the Assistants API in favor of the new Prompts + Responses + Conversations model. According to the migration guide, Assistants will shut down on August 26, 2026, and existing integrations are expected to move over to Prompts created in the dashboard.

The current PHP SDK already supports Responses and Conversations, but there is no support for Prompts, which OpenAI describes as the direct successor to Assistants. Prompts are now the required way to define model configuration, instructions, tools, and structured output contracts. They can only be created and versioned in the dashboard, but applications must still reference them by ID and interact with them through the API.

Since prompts replace assistants as the primary configuration object, it would help to understand what the plan is for adding prompt-related endpoints or helpers in this SDK.

A few questions:

• Is prompt support planned for the SDK?
  Even if prompts are created only in the dashboard, referencing them, resolving versions, or retrieving their specs would be important for production setups.
• Will there be a dedicated resource like $client->prompts()?
  The migration guide positions prompts as a first-class object in the API model, so it would be helpful to know whether this SDK intends to expose a resource for them.
• If support is planned, is there an expected timeline or roadmap?

Given that the SDK already marks Assistants, Threads, and Runs as deprecated, it would be great to know how the maintainers intend to cover the new workflows that rely on prompt IDs as the main configuration entry point.
Thanks in advance for any clarification, and thanks for your work maintaining the PHP client.

Start by reviewing the existing Responses and Conversations resources, then compare them with the deprecated Assistants, Threads, and Runs resources and the migration guide. Determine the intended prompt-related API surface, including referencing prompt IDs, version handling, and resource naming; done means a maintainer-approved implementation scope and roadmap for exposing Prompts in the PHP client.