STORE PACKAGE
AGPL-3.0 · SELF-HOSTED · YOUR KEYS

Creative · Store package · v1.4.0

Vids Studio

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

Vids Studio

What it does

The rest of the story.

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

Tools the bot can actually call.

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

What happens when you use it.

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.

  1. 01

    You open it, or the assistant does

    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.

  2. 02

    Or you just ask

    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.

  3. 03

    A named bot picks it up

    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.

  4. 04

    Longer work becomes a ticket

    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.

  5. 05

    The result lands where you can check it

    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

You can ignore this app entirely and just ask.

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.

Accountability

4 capabilities, each attached to a named identity.

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.

veo-prompt-craftvids-generatevids-operateshot-planning

Also on the creative shelf

Apps that pair with this one.

All 11 creative apps →

Underneath

What every app on this site is standing on.

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.