fix: bound video agent phases and enforce native output budgets - #29
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.
|
devhims
force-pushed
the
fix/agent-phase-deadlines
branch
from
September 8, 2026 14:23
e959ced to
b93b25e
Compare
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.
The video agent now gives classification, research and finalisation separate persisted deadlines, rejects tasks outside supported YouTube synthesis, and uses native structured output and SDK token ceilings for final answers. Compact transcript notes and concise answer guidance reduce generation work while retaining source references and caveats.
Changes
Validation
Remaining limitations and deployment
Native token limits and schema validation do not guarantee that every answer fulfills the requested scope or finishes before its deadline. Detailed-report timeouts and schema-valid incomplete answers remain unresolved. The recovered upstream response rules out client-side truncation for the investigated failure, but model generation versus provider serving remains unresolved.
Requested-count enforcement and inference reliability remain follow-up work. An alternative model provider is explicitly deferred.
The latest SDK-budget changes have not been manually deployed. Cloudflare's connected build pipeline watches main, so merging this PR will trigger verification and production deployment. This PR does not claim that every request completes successfully within 100 seconds.