feat: make video agent responses adaptive and compact by default - #24
Merged
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
The video agent imposed a default three-item recommendation list and short recovery answers even when users requested more. Answers now follow the requested count and detail, with evidence-backed output capped at 20 blocks. Transcript analysis and recovery budgets support the larger scope, and warnings distinguish source uncertainty from an actual unanswered part of the request.
Compact responses are now the default for admission and polling. Clients requiring the previous envelope must pass
responseFormat=legacy. OpenAPI, local testing instructions, and the live test script are updated.Validation:
Two focused commits separate answer-scope changes from the compact-default change. Production verification will follow after both PRs merge and deploy.