DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.
Storage handle threaded into client creation and MCP calls
Under the hood
Useful1Signal2
Internals
Credential access keeps migrating onto one shared handle across client and MCP paths.
What's wrong with this entry?
Anonymous. No account, no email.
What
The API client factory now takes a storage handle and passes it to the pre-request auth refresh and the custom fetch builder, and the headless MCP call path passes it where it used to pass an app-state setter. Continued migration of credential access onto one handle.
Evidence
callMCPToolWithUrlElicitationRetry
Strings lifted out of the shipped bundle, so the claim above can be checked against them.