feat(agent-cache/ai): cache streaming LLM responses via wrapStream#262
Open
amitkojha05 wants to merge 1 commit into
Open
feat(agent-cache/ai): cache streaming LLM responses via wrapStream#262amitkojha05 wants to merge 1 commit into
amitkojha05 wants to merge 1 commit into
Conversation
baade71 to
13371cd
Compare
13371cd to
e938a50
Compare
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The agent-cache Vercel AI SDK adapter currently implements
wrapGeneratefor non-streaming calls. Streaming responses are not cached, requiring callers to manually accumulate streamed content and invokestore()themselves.This PR adds support for
wrapStream.On a cache miss, the upstream stream is tee'd:
text-deltachunks and stores the final response viacache.llm.store()onfinish.On a cache hit:
doStreamis skipped entirely.text-deltaevent followed by afinishevent.Tool-call streams are not cached, matching existing
wrapGeneratebehavior.Additional guarantees:
check()failures fall through to the upstream provider.wrapGenerateconsumers are unaffected.Changes
adapters/ai.tssynthesizeStreamFromCached()accumulateAndStore()wrapStreamto the middleware return objectwrapGeneratebehavioradapters/__tests__/ai.test.tsAdded 5 new tests:
providerMetadataincluded on cache hitsCHANGELOG.mdREADME.mdTesting
pnpm --filter @betterdb/agent-cache test pnpm --filter @betterdb/agent-cache build