Update Preview escalation context contract - #632
Merged
Conversation
Co-Authored-By: Claude <noreply@anthropic.com>
mckenna
force-pushed
the
peter/fin-agent-api-escalate-context
branch
from
August 25, 2026 11:28
9649602 to
5b77fa5
Compare
rahulgdsouza
approved these changes
Aug 25, 2026
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
2 participants
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.
Why?
The Preview contract still documented an unsupported
messagefield and outdatedcontextbehavior, which could cause clients to send invalid requests.How?
Updates the escalation contract so
contextworks with either input path, is limited to 10,000 characters, and appears in the new Helpdesk conversation's internal note without being shown to the end user. Removesmessageand clarifies that escalation does not close the source conversation.Companion PRs:
Generated with Claude Code