Creative · Store package · v1.4.0
Turn an idea into generated video - the Veo specialist drives Google Vids by clicking, in a remote operator's logged-in Chrome: describe the shot, it generates the clip and places it on the timeline.
Opens ?app=vids on the demo deployment. On your own box it is the same URL.
1 screen in the ribbon · opens on vids-studio
What it does
Job + multi-scene Extend-story dispatch to the registered desktop worker, with the job-queue surface behind the cockpit tile. The shared vids-operator desktop worker (the ADR-080 story engine lives in its content.* tools), its registry entries, the remote-client mesh, and the oshal-vids CLI stay framework-resident; this package is the surface over them.
What you can ask it
Registered server-side, scoped to the signed-in user. The bot calls the tool — it never shells out, and it never handles the credential behind it.
How it runs
Not a chat window with a plugin behind it. Every step below is something the app declares in its manifest, which is why it can be told to you plainly.
Opening ?app=vids loads its 1 screen into the shared cockpit, starting on vids-studio. The ribbon, the ticket list and the assistant are already there — the app contributes views, not a second application to log into.
The assistant classifies what you asked for and hands it to the bot that owns that domain. You do not pick the app, and you do not learn a command — routing is by declared capability, not by keyword matching a menu.
vids-operator is accountable for the work. 4 declared capabilities say what it is trusted to do; the tokens and dollars it spends are recorded against that identity, so the cost has a line item rather than disappearing into a monthly bill.
Scheduled and swarm-initiated work enters the queue as a vids ticket. It is durable, it has an owner, you can watch it move through its phases, and if it fails it fails somewhere you can open and read.
Back on the app's own screens, as state you own — not as a chat message you have to scroll back to find.
With the assistant
The assistant is the front door. It classifies your request, delegates to the bot that owns the domain, and answers in one voice — so you do not have to know which of the applications this happens to live in.
vids-operator advertises what it is accountable for, and the assistant matches against that.Accountability
Declared in the manifest and bound to the bot above — so "what is this thing allowed to do" is a list you can read, not a prompt you have to trust.
Also on the creative shelf
On-brand OSHAL motion graphics — a short brief becomes the validated electric-"oshal" intro look via Google Vids on the operator's signed-in Chrome
Learn more → CreativeStoreRemote camera control - connect a GoPro (Open GoPro HTTP) or other cameras as device nodes and drive them: record, photo, modes, settings…
Learn more → CreativeStoreA creative bot that just keeps making short kid-safe videos - it rotates a public-domain library (fables, fairytales, famous sayings), animates each…
Learn more → CreativeStorePlay D&D with an AI Dungeon Master on a cinematic shared board: claimed heroes and visible AI companions follow an explicit move, action, target…
Learn more →Underneath
This app does not ship its own queue, its own credential store or its own cockpit. It declares what it needs and the platform provides it.