1.0.0-rc.5

AgJSON 1.0.0-rc.5: a cut-off Vercel AI SDK stream closes as an interruption

The fifth release candidate for 1.0.0. All six packages move to 1.0.0-rc.5 together. The spec doesn’t change: they still ship spec revision 1.0.0-rc.3 (AGJSON_VERSION).

Installing the release candidate

The release candidate is published under the rc tag. latest is on 0.12.9:

npm i @silverprotocol/core@rc

Install each framework package you use the same way, so every @silverprotocol/* package in your lockfile is on 1.0.0-rc.5. While a release candidate is the most recent publish, a package’s page on npmjs.com shows no README; each package still carries its README.

0.12.9 ships the same Vercel AI SDK fix on the 0.12 line, and 1.0.0-rc.5 carries everything 0.12.9 changes.

Who should upgrade

  • You run the Vercel AI SDK with @ai-sdk/openai 4.0.100 or later. A stream cut off before its completion signal now closes as an interruption, where rc.4 closed it as a success.
  • Anyone else gets the same output as from rc.4: all 446 replayed runs are byte-identical (see Wire version).

Upgrading from rc.4

  • Vercel AI SDK: a cut-off stream now closes turn.abort with reason "interrupted", not a success turn.done. From @ai-sdk/openai 4.0.100, the provider starts every stream (Responses, Chat Completions and Completions) at finish reason interrupted and moves off it only when its completion signal arrives, so a stream cut off mid-answer ends with finish-step and finish both interrupted. From ai 7.0.149, interrupted is a member of FinishReason and stops the step loop. rc.4 closed that turn as a success turn.done, with finishReason "unknown" and finishReasonRaw "interrupted". rc.5 closes it turn.abort with reason: "interrupted", as the spec requires for a native interruption (§8.0 item 17), and each step’s usage still rides its finish-step’s message.end. A UI that renders a success turn as complete now shows a cut-off answer as stopped. With @ai-sdk/openai 4.0.99 or earlier, the provider reports a cut-off stream as other and gives no interruption signal, so the same stream closes turn.done with finishReason "other", on this version and every earlier one.

Google ADK

  • With @google/genai 2.31.0, an error the service sends mid-stream is reported. From genai 2.31.0, an error that arrives as an event of an SSE stream (a rate limit or an overloaded model after the stream began) reaches ADK as a thrown error, and ADK 2.3.0 reports it as an in-band error with error code UNKNOWN_ERROR and the HTTP status inside its message. The package emits an error event and closes the turn turn.error, as for any in-band error (§8.0 item 35). Under genai 2.30.0 the same stream lost the error: a stream with text before the error closed turn.abort "stream-truncated", or a success turn.done with the host-completion event, and an error-only stream opened no turn. The package’s code doesn’t change; its README documents this.

Spec

Unchanged. The packages ship spec revision 1.0.0-rc.3, as rc.4 did, so no closed set, schema or fold rule changes.

Verified versions

Each framework package is verified end to end, tool calls included, against a live run at:

  • @anthropic-ai/claude-agent-sdk 0.3.310;
  • @openai/agents 0.21.0;
  • @google/adk 2.3.0, with @google/genai 2.31.0;
  • ai 7.0.153, with @ai-sdk/openai 4.0.102.

Wire version

1.0.0-rc.3, unchanged. Replaying every recorded stream and engine-built fixture through the 1.0.0-rc.4 and 1.0.0-rc.5 packages, all 446 runs give byte-identical events: 85 recorded streams and 361 runs of the engine-built Google ADK and OpenAI fixtures. No recorded Vercel AI SDK stream carries the provider’s interrupted finish reason. A cut-off stream built from parts captured at ai 7.0.153 with @ai-sdk/openai 4.0.102 closes turn.done on rc.4 and turn.abort "interrupted" on rc.5, and the same stream run to completion closes turn.done on both.

The 1.0.0-rc.5 packages are built from typescript-sdk commit 3aa8e45b, the commit npm’s provenance for all six 1.0.0-rc.5 packages attests.