1.0.0-rc.7
The seventh release candidate for 1.0.0. All six packages move to 1.0.0-rc.7 together. @silverprotocol/core, @silverprotocol/google-adk and @silverprotocol/claude-agent-sdk change; the other three have no code change. The spec doesn’t change: the packages 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.11:
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.7. 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.11 ships the same @silverprotocol/core fix and the same three Google ADK fixes on the 0.12 line, and 1.0.0-rc.7 carries everything 0.12.11 changes.
Who should upgrade
- You run Google ADK in
StreamingMode.SSEwith a planner that writes state (@google/adk2.4.0). Streamed text rendered twice on rc.6; it now renders once. - You run Google ADK on the Interactions route (
useInteractionsApi) inStreamingMode.SSE. A response’s text now renders once, and the response closes one turn. - Your Google ADK tools return function responses with
parts,schedulingorwillContinue. Those members now reach the stream; rc.6 dropped them. - You resume Claude Agent SDK sessions (
@anthropic-ai/claude-agent-sdk0.3.317 or later). A session whose writes were lost on a full disk is now reported. - Anyone else gets the same output as from rc.6: all 448 replayed runs are byte-identical (see Wire version). Read “Upgrading from rc.6” first: the message-thread change applies to every framework package’s output.
Upgrading from rc.6
- A message lands on its turn’s thread. When a
message.startnames athreadIdother than the one its turn already has (from the turn’sturn.start, from its parent’s thread for a nested turn, or from an earliermessage.start), the reducer now creates the message on the turn’s thread. rc.6 kept themessage.start’s ownthreadId. The turn record’s thread doesn’t move, and the fold doesn’t resync. Amessage.startfor a turn that has no thread yet still gives the turn its thread. - Google ADK: an unmatched function response that holds credential material is no longer carried. A
functionResponsethat carries no id (or an empty one) and answers no pending call under its name ridesext.google.unparsedwhole. When it holds an ADK credential object or a response toadk_request_credential, at any depth, the package now emits one non-terminalerrorevent in its place, withcode"adk_orphan_credential_response"and a fixed message, and nothing of the response rides (spec §8.0, graceful degradation). rc.6 carried such a response whole, credential members included. Theerrordoesn’t close the turn. An unmatched response without credential material still rides whole, a reply namedadk_request_credentialkeeps its allowlisted carry, and a response that answers a call still maps totool.done. A credential an application keeps in a shape of its own isn’t recognised, and rides unchanged.
@silverprotocol/core
- The message-thread change above. No other fold rule changes.
Google ADK
- A planner’s state record no longer doubles streamed text. From
@google/adk2.4.0, with a planner that writes state, ADK yields an event that only records the state change inside a model call, between its streamed chunks and its repeat of them inStreamingMode.SSE. rc.6 read that event as the end of the call, so the repeat rendered the text a second time. The record still maps to itsstate.delta, and it now holds the match open for its source’s next event: a chunk, apartial: falserepeat or another such record keeps it, and any other event of the source ends it first. Events of other sources don’t touch it. The repeat renders nothing, as without the record. - A repeated close of an Interactions response maps once. On the Interactions route (
useInteractionsApi) inStreamingMode.SSE, ADK closes a response atinteraction.completedand again when the stream ends, and acompletedstatus update can close it once more, each time with every part so far. rc.6 rendered the response again at the second close. A close that maps to exactly what the response’s previous close mapped to, itsidandtimestampaside, with no other event of the response between them, now emits nothing: the response renders once and closes one turn, with or without the host-completion opt-in. A close with any mapped difference maps as before, and apartial: falseevent ADK yields mid-response (a media part, a finished function call) is not a close and always maps. - A function response’s
parts,schedulingandwillContinueare carried. Atool.donehas no slot for these members of a genaiFunctionResponse, and rc.6 dropped them. They now ride oneprovider-rawblock, verbatim, right before that call’stool.done, with the response’s own name and id. The carried value is reduced like every otherprovider-rawcarry (spec §8.0 item 28), and a reply toadk_request_credentialnever takes it. A response without these members maps as before. - The unmatched-response change under “Upgrading from rc.6”.
Claude Agent SDK
- A session whose writes were lost is reported. From
@anthropic-ai/claude-agent-sdk0.3.317, the CLI sends asystemmessage with subtypesession_writes_lostas it exits when the disk was full or over quota and lines of a session transcript or changes to~/.claude.jsonwere not saved. rc.6 emitted nothing for it. It now ridesext.anthropic.framewith kindsession_writes_lost, verbatim, after the turn’s close, and the turn’s outcome doesn’t change. A host that resumes one of the sessions it lists may find part of that conversation missing.
Vercel AI SDK
- With
@ai-sdk/openai4.0.110 or later, an OpenAI Responses refusal reaches the stream. From 4.0.110, the provider streams a refusal as the assistant’s text and finishes the step withcontent-filter. This package maps that finish, as before, toturn.donewithfinishReason"safety_blocked", and sets nofinishReasonRawfor it. With 4.0.109 or earlier, the refusal text never reached the stream: the host saw an empty assistant message, and the turn closed withfinishReason"stop". The package’s code doesn’t change.
OpenAI Agents SDK
- No code change. The package is now verified over the
openaiclient 7.53.0, where rc.6 was verified over 7.22.0. Of the Responses fields the client typed in between, the usage detailcache_write_tokens_details(7.50.0) would ride the existingusage-detailsevent, though no recorded stream carries it yet.tool_usage(typed in 7.46.0) andimage.context_compression(7.51.0) are not carried.
Spec
Unchanged. The packages ship spec revision 1.0.0-rc.3, as rc.6 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-sdk0.3.319;@openai/agents0.21.0;@google/adk2.4.0, with@google/genai2.32.0;ai7.0.166, with@ai-sdk/openai4.0.111.
Wire version
1.0.0-rc.3, unchanged. Replaying every recorded stream and engine-built fixture in the release’s test corpus through the 1.0.0-rc.6 and 1.0.0-rc.7 packages, all 448 runs give byte-identical events. The replay compares the events each package emits, not a fold of them, and no recorded stream or fixture carries an unmatched credential response, a function response’s new members, a planner’s state record, a lost-writes message or a stream on the Interactions route; those changes rest on their own tests. A live capture on the Interactions route, recorded outside that corpus in StreamingMode.SSE at gemini-3.8-flash, shows the repeated-close fix: rc.6 renders the response twice, in 30 events, and rc.7 renders it once, in 19.
The 1.0.0-rc.7 packages are built from typescript-sdk commit e06c4523, the commit npm’s provenance for all six 1.0.0-rc.7 packages attests.