fix(prompt): keep volatile context outside cache - #1838
Closed
sentry-junior[bot] wants to merge 2 commits into
Closed
sentry-junior[bot] wants to merge 2 commits into
sentry-junior[bot] wants to merge 2 commits into
Conversation
Co-Authored-By: Dave Rosenthal <david.rosenthal@sentry.io> Co-Authored-By: David Cramer <david@sentry.io>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
1 participant
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.
A short first model call could write several thousand prompt-cache tokens because Pi places its Anthropic cache marker on the current user message, after Junior's volatile runtime context.
This change moves the mostly stable capability catalog into the system-prefix area. It also adjusts the first request payload for a Turn so the cache marker ends before
<runtime-turn-context>. Later tool-loop calls keep Pi's normal history caching behavior.The change keeps actor, configuration, runtime, plugin request context, and the current request outside the cache boundary.
via Dave Rosenthal.
--
View Junior Session [Sentry]