@warlock.js/ai-openai 5.26.0 → 5.27.0

package/CHANGELOG.md

@@ -4,6 +4,14 @@ All notable changes to `@warlock.js/ai-openai` are documented in this file.
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/). `@warlock.js/*` packages are released in lockstep — every package shares the same version number, so a version below may list only the changes that affected this package.
 
+## 5.27.0 - 2026-10-01
+
+### Added
+
+- **Responses API (opt-in).** `sdk.model({ name, api: "responses" })` routes an OpenAI model through `/v1/responses`, so a reasoning model (gpt-5 family, o-series, gpt-6) can use function tools with reasoning on. Chat Completions stays the default and is unchanged. Under `api: "responses"` reasoning uses the provider default even when tools are attached (more reasoning tokens and latency than the Chat path, which forces reasoning off with tools); the system prompt is sent as `instructions`; requests use `store: false`; `pdf`/`audio` inputs are off. Only the `openai` provider accepts it: the DeepSeek, Groq, xAI and Mistral adapters reject `api: "responses"`.
+- **Responses streaming.** `stream()` works under `api: "responses"` and yields the same chunks as the Chat path: text deltas (refusal text included), then the tool calls, then one `done` with the finish reason and usage. A `response.failed` or `error` event mid-stream throws the same typed error as a failed request.
+- **Reasoning replay across tool turns.** Every Responses request asks for `include: ["reasoning.encrypted_content"]`. The reasoning items of a tool-calling turn are saved on the first tool call (`providerMetadata.openaiResponses = { model, reasoningItems }`) and sent back before that turn's function calls on the next request, so the model keeps its own reasoning while it works through tools, with nothing stored on OpenAI's side. Replay is skipped when the model changed, and turns without a tool call are not replayed. **The encrypted reasoning items are stored with the conversation history** (memory or session store), so expect larger stored messages; there is no size cap. The Chat path and the other adapters ignore the key.
+
 ## 5.26.0 - 2026-09-30
 
 ### Changed