Feature/omni flash - #30
Merged
Merged
Conversation
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.
Summary
Adds Gemini Omni Flash video support to FlowKit, including generation endpoints, model configuration, REST API exposure, and workflow-backed polling/download handling.
Closes #23.
What’s included
Workflow polling / download fix
Omni Flash generation responses use workflow-backed media and do not work correctly with FlowKit's legacy video polling path.
In particular, using:
GET /v1/media/{primaryMediaId}for Omni workflow media currently returns
400 INVALID_ARGUMENT.This PR follows the current Flow UI behavior instead:
flow.projectInitialDataendpoint.primaryMediaId.MEDIA_GENERATION_STATUS_SUCCESSFUL.media.getMediaUrlRedirect.This also addresses the polling/download issue reported in #23 by @TIMMY-xyz.
Implementation notes
Omni model keys are kept configurable in
agent/models.json, since Google's internal Flow model identifiers may change independently of FlowKit releases.Omni polling is intentionally kept separate from the existing legacy Veo operation polling because the workflow handles returned by Omni are not accepted by
batchCheckAsyncVideoGenerationStatus.Validation
The implementation includes unit coverage for:
The Omni generation and workflow-media path was also tested against the live Flow service while developing the implementation.