| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Hey! Your PR title Add token caching for any amazon-bedrock provider doesn't follow conventional commit format. Please update it to start with one of:
Where scope is the package name (e.g., app, desktop, opencode). See CONTRIBUTING.md for details. |
Sorry, something went wrong.
|
The following comment was made by an LLM, it may be inaccurate: Based on the search results, I found potentially related PRs: Related PRs Found:
These PRs are related to the token caching and bedrock provider enhancements. You may want to check if any are duplicates or if they should be consolidated. |
Sorry, something went wrong.
|
#16504 addresses the same problem, but is wider in scope. If that PR is merged, then this PR can be closed. But I made this PR in the hopes that a smaller and more focused PR would get reviewed and approved to fix my immediate problems sooner. |
Sorry, something went wrong.
|
@rekram1-node Running into this problem as well, if you have a chance to take a look :) |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Issue for this PR
Partially addresses #5416 as it now allows token caching for custom providers that use the "@ai-sdk/amazon-bedrock" package.
Type of change
What does this PR do?
If the model provider is anthropic or contains bedrock, then we enable message-level token caching. But if a user has a custom provider which uses the "@ai-sdk/amazon-bedrock" npm package it will try to perform content-part level token caching, which will result in no caching taking place.
How did you verify your code works?
I built a representative test to check that the change works. I haven't been able to run an end-to-end test though because my environment that communicates with AWS can't communicate with the outside world, and so bun install doesn't work. And outside of this environment I don't have AWS bedrock access.
Checklist