ta
TanStack
GitHub
ai
Workspace
GitHub
CI Pipeline Executions
Filtered
Runs
Demo
Insights
Compare tasks
Analytics
Sign in
Toggle sidebar
Overview
⌘K
ai
Loading workspace stats
Loading workspace insights...
Statistics interval
7 days
30 days
Latest CI Pipeline Executions
Status
Fix filter
Filter
Fuzzy
Filter range
Sort by
Sort by
Start time
Sort ascending
Sort descending
Succeeded
871-support-gemini-omni-flash-gemini-omni-flash-preview-via-the-interactions-api
5ffa1665 Merge fb513c7b3a8a951bdca623f03fecaa6860f1720f into e3de949575eac8301c0449afa3a91ef450e9580b
by Tom Beckenham
T
Succeeded
871-support-gemini-omni-flash-gemini-omni-flash-preview-via-the-interactions-api
5ffa1665 feat(examples): Omni Studio conversational session view in ts-react-media Add a chat-style session tab built around Gemini Omni Flash's conversational editing: - Timeline of turns where each completed clip auto-becomes the continue-from target; "Continue from here" branches the session from any earlier clip via previous_interaction_id - Multi-reference image tray (Omni supports ~6), single reference clip slot labeled with the 3s API limit, and a prompt-steered audio direction field - Per-turn duration slider (3-10s) doubling as a $0.10/s cost estimate, aspect toggle, and task-mode pin mapped to generation_config.video_config.task - Duration is locked and omitted for edit-shaped requests (continuing a clip, task=edit, or attached clip without a reference pin) — Omni rejects durations that don't match the source clip's length - Failed turns get an "Edit & retry" button that restores the prompt, attachments, and settings to the composer and removes the dead turn createVideoJobFn gains omniOptions (duration / aspectRatio / task) to carry the new controls. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
by Tom Beckenham
T
Succeeded
871-support-gemini-omni-flash-gemini-omni-flash-preview-via-the-interactions-api
6da3cdab fix(ai-gemini): address PR review findings for Omni Flash video - Reject out-of-range Omni durations at job creation with a clear local error instead of silently passing them to the live API - Map requires_action interactions to a failed status so polling can't spin until timeout (reachable via previous_interaction_id chaining) - Surface failed job statuses in the ts-react-media example instead of polling forever on a pending spinner - Add a compile-time regression test guarding the generateVideo VideoAdapter generic-arity fix, plus unit tests for duration rejection, fractional pass-through, and requires_action mapping - Fix stale doc/comment claims: Veo 2/3 model lists, "fixed 10s" clips, "clamped" duration wording, and content-block ordering (images, then videos, then text) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
by Tom Beckenham
T
Succeeded
871-support-gemini-omni-flash-gemini-omni-flash-preview-via-the-interactions-api
6da3cdab Merge b427cc4195ee82d62e6a8546393c3b89df464b81 into fe5d788a0c90e1672cdc66db0a99879679750e02
by Tom Beckenham
T
Succeeded
871-support-gemini-omni-flash-gemini-omni-flash-preview-via-the-interactions-api
d6bc7ff5 feat(ai-gemini): support Omni Flash 3-10s clip durations The issue's live verification concluded Omni clips were a fixed 10 seconds, but response_format.duration is a real request field — just undocumented. Verified against the live API: it takes a "<seconds>s" string, accepts any value in the 3-10s range including fractional seconds (a 3s request returns a 3.008s MP4 per ffprobe), rejects out-of-range values with explicit minimum/maximum errors, and defaults to 10s when omitted. Omni's duration is now typed number with availableDurations() = { kind: 'range', min: 3, max: 10, unit: 'seconds' } and snapDuration clamping into it; the adapter maps the generateVideo duration option onto response_format.duration. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
by Tom Beckenham
T
Failed
871-support-gemini-omni-flash-gemini-omni-flash-preview-via-the-interactions-api
d6bc7ff5 Merge 68b1340a6458e71459d299c4b55962073fc1ad64 into f8b145ff21fd44ff37a15014e1d4bd58139d9dc6
by Tom Beckenham
T
Succeeded
871-support-gemini-omni-flash-gemini-omni-flash-preview-via-the-interactions-api
1eb40b59 feat(examples): Gemini Omni Flash with all inputs in ts-react-media Add gemini-omni-flash-preview (text-to-video + image-to-video) to the ts-react-media example, exercising every Omni input: text prompts, a start image, an attached reference/edit video clip (Omni-only — never sent to other providers), and conversational editing that chains a new prompt onto a completed generation via previous_interaction_id. Also fixes a latent core type bug this surfaced: generateVideo / getVideoJobStatus constrained adapters as VideoAdapter<string, any, any, any>, leaving the duration generic at its Record<string, number> default — any adapter with a narrowed per-model duration union (Omni's 10, Veo's 4|6|8) failed assignability under strict function-type contravariance. All video-activity constraints now span all six VideoAdapter generics. Verified live: Omni edit chaining (previous_interaction_id) against the real Gemini API returned an edited 10s MP4; example dev server boots and type-checks. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
by Tom Beckenham
T
Failed
871-support-gemini-omni-flash-gemini-omni-flash-preview-via-the-interactions-api
1eb40b59 Merge b4321f4642e7351efa709119d07a8a8d2becf898 into f8b145ff21fd44ff37a15014e1d4bd58139d9dc6
by Tom Beckenham
T
Previous
Next