Lyria 3 Clip does not read team materials or open a signed-in browser. It is an audio generation model, not an agent: Google lists no function calling or URL context for it. For a short team sound concept, let a local text agent use Tabbit CLI to read an authorized page in Tabbit Browser, then prepare a named review draft. Generate a separate 30-second clip only if the brief is approved, the Google service exposes lyria-3-clip-preview, and the team has authorized that use. Stop before publishing.
Install Tabbit Browser and Tabbit CLI on the same machine, then install the Tabbit skill in your local agent client using that client’s documented setup.
That boundary keeps browser access, music generation, and sharing as three separate decisions. Google’s current Cloud page lists Clip as Preview, with one 30-second MP3 per prompt.
Key takeaways
A local agent reads the signed-in team page; Lyria Clip only generates audio.
Use Tabbit Browser and the Tabbit CLI skill from a client running locally alongside the browser. Pi uses
/skill:tabbit; other clients may use a/skillspicker or a documented command.Google Cloud lists text and image inputs, 30-second output, one clip per prompt, and 44.1 kHz MP3.
Draft the brief first. Create a shared document only when the destination is authorized and a connected tool confirms write access.
Generate a clip only after approval; review the full audio and stop before any public upload.
Three separate permissions
| Layer | What it does | What to verify |
|---|---|---|
| Local text agent + Tabbit CLI | Reads approved fields in the signed-in page and returns a structured brief | Client discovers the skill, CLI connects, page title/status match, and local account can read the page |
| Google Lyria 3 Clip | Turns an approved prompt or image into one short audio clip | The selected project/service lists exact ID lyria-3-clip-preview and grants generation access |
| Shared document or publishing destination | Stores a review draft or distributes a final asset | User authorized the named location, connector confirms write access, and a reviewer approves final use |
The official Google Cloud Lyria page lists Clip as Preview, released March 25, 2026. It supports text-to-music and image-to-music, vocal or instrumental mode, generated or supplied lyrics, and a 30-second clip. It allows BPM and intensity controls; detailed structure controls are not listed for Clip. Its technical output is one MP3 at 44.1 kHz and 192 kbps. The Gemini API deprecation page lists no announced shutdown date for Clip. Check the current service selector before assuming your API project has access.
Lyria Clip does not operate the browser. Google’s model documentation says the audio models do not support function calling or URL context. A text agent and the music model are separate tools. The client also matters: it must have an available text model, provider authentication, a local shell route to Tabbit CLI, and a skill interface that actually discovers Tabbit. The Tabbit skill documents /tabbit examples for some clients; Pi documents /skill:tabbit, and some clients expose /skills. Read the Tabbit CLI setup guide and Codex Tabbit CLI setup for client-side distinctions.
Read a team page without copying the whole document
Open the team brief or asset request in Tabbit Browser. Sign in yourself and confirm the right account, project, title, and approval status.
Check the client can see the Tabbit skill. Separately run
tabbit-cli diagnose; these checks answer different questions.Ask a local agent to read only the fields needed for a music brief: approved scene, intended audience, duration, permitted references, and review owner.
Keep source links with each extracted point. Do not paste full internal notes, customer details, credentials, or unpublished names into a third-party music prompt.
Review the output in your regular browser tab. The CLI task runs in its own task tab, so you can keep using other tabs. See connect an agent to an existing browser and browser agent first-task checks.
The existing website login stays in the selected Tabbit Browser environment. The CLI does not sign in for you. If a page is inaccessible or asks for authentication, stop and handle it manually. A local fixture check recorded in this worktree confirmed that one named CLI task could read a test page after a separate sign-in action. That verifies only the fixture’s session reuse, not a shared-document integration or successful Lyria generation.
Create a named review draft
When a connected shared-document tool is authorized for a specific destination, ask the agent to create a review draft there. Do not treat the Tabbit CLI as document write permission. If no document connector is available or authorized, ask for the same draft in the local agent conversation and let a human paste it into the team workspace.
Use Tabbit CLI in the current Tabbit Browser profile. Read the team brief I opened.
If the page is not marked Approved for music exploration, stop and report its title and status.
Do not change the source page or upload an audio file.
Extract only: approved project name, audience, scene, intended feeling, permitted assets,
clip length, and reviewer. Keep the source URL beside each extracted fact.
Draft a 30-second Lyria 3 Clip prompt using broad genre terms, BPM range, instruments,
energy, and instrumental/vocal choice. Do not name an artist or quote lyrics.
Create a shared document titled “Aurora launch sting — music review draft” only if this
client has an authorized document connector and the destination is the team’s approved
review space. Include the source link, the extracted brief, the prompt, a blank field for
the generated clip URL, and the reviewer’s name. Save as a review draft. Do not publish.
If no authorized document tool is available, return the same content here instead.
Stop for human review before generating or sharing anything.
Expected output: named draft location (if created), source-linked brief, one prompt,
and an explicit note that no clip was generated or published unless separately authorized.The named title is an example, not an existing shared file. This task environment has no verified shared-document write path for this article, so the workflow stops at a draft in the local agent conversation. Do not state that a document or audio clip was created unless the relevant tool confirms it. For more on drafting without submitting, see browser-agent CMS draft workflows and the first browser task checklist.
Generate and review a short Clip
Once a human approves the brief and confirms the Google service is authorized, open its music generation surface separately. Select the exact lyria-3-clip-preview ID. A similar display name or a third-party router is not proof that the request reaches Google’s model. Use only the allowed brief fields and permitted assets.
| Review stage | What to compare | Stop before |
|---|---|---|
| Approval check | Page title, Approved status, owner, and source | Brief is pending or the reviewer is missing |
| Prompt check | Scene, audience, broad style, BPM, instruments, vocal mode | Prompt names an artist, includes private content, or makes unsupported claims |
| Clip check | 30-second duration, beginning/end, intelligibility, tone, watermark notice | Audio departs from brief or rights/terms are unclear |
| Sharing check | Draft clip URL, named review destination, reviewer decision | Public upload, campaign scheduling, or distribution has not been approved |
Google Cloud describes a 30-second maximum and one clip per prompt. The model page lists 44.1 kHz and 192 kbps MP3, audio watermarking, and content filtering. The team should listen to the whole preview rather than approve from a generated title or thumbnail. Consult the Lyria model card and the terms for the exact Google service; Google Cloud Preview terms allow commercial use only subject to the controlling agreement and restrictions.
What the community evidence can support
Two Reddit users who described trying Lyria report different impressions of vocal naturalness and prompt fit. One separate Pro user praised a requested guitar fade but said aggressive genres felt too safe. These are subjective reports from early versions, not controlled tests of your account, current Clip build, or browser workflow. We did not find a verified first-hand report specifically about lyria-3-clip-preview in the pages reviewed. See researching with browser sources and local browser task validation for evidence boundaries.
End at the human review checkpoint
Use a local Tabbit task when you need a browser agent to gather a few approved fields from a signed-in team page. Use Lyria Clip in its own supported Google surface to make the short audio preview. Keep the named shared-doc draft in a tool-authorized workspace, or in the agent conversation if no such access exists. A human listens, checks rights and terms, and decides whether to publish. Browser MCP versus CLI and browser research with sources cover the local handoff and evidence workflow.
FAQ
Can Lyria 3 Clip read our team documents?
No. Lyria 3 Clip generates music and its model page lists no URL context or function calling. A separate local text agent can read an authorized page through Tabbit CLI, then prepare a brief for a human review.
What is the exact Lyria 3 Clip model ID?
Google Cloud lists `lyria-3-clip-preview` as a Preview model released on March 25, 2026. The Gemini API deprecation list currently shows no shutdown date for Clip. Confirm the ID in the specific Google service you use.
How long is a Lyria 3 Clip output?
The official Cloud documentation says Clip generates one 30-second MP3 per prompt at 44.1 kHz. It supports BPM and intensity controls; detailed structure controls are listed for Pro, not Clip.
Can Tabbit CLI create a shared Google Doc?
Tabbit CLI provides local browser control; it does not grant a client permission to create shared documents. Use a connected document tool only when the user authorized the destination and the tool confirms write access. Otherwise return the draft in the agent conversation.
Can I use a team page’s private material in a music prompt?
Only use material you are authorized to disclose to the selected Google service. Ask the local agent to extract approved fields and leave out confidential text, names, credentials, and customer data.
Can I publish a generated Clip immediately?
No automatic publish step is part of this workflow. Listen to the full clip, compare it with the approved brief, review the applicable Google service terms, and get a human approval for the named destination first.