Images, video, and audio

Media tasks usually take longer than text generation and can involve paid models. Decide the purpose, the specifications, and the reference sources before you start generating.

Images and covers

Prepare the title, a body summary, the platform, the aspect ratio, and reference images. People, products, brands, or recurring scenes should go into the subject library first, so describing them again and again does not produce inconsistent visuals.

When generation finishes, attach the results you chose to the draft or project, and keep the rejected versions for the review.

Video

A video task starts from a script, a shot list, an asset checklist, and output specifications. Long tasks are best split into verifiable media tasks, but everything still has to come back to the same draft or project package.

An external Agent can plan, submit tasks, and read status; large files, rendering, and the final video stay in Beav. Agents should reference tasks or artifacts, never inline video content into the chat context.

Audio and subtitles

Audio tasks can include narration, music, sound effects, transcription, and subtitles. Confirm the language, the voice, the duration, and where it will be used before generating. Bind subtitles to the exact video version, so an old timeline is not reused after the video changes.

Cost and approval

Paid generation needs confirmation before it runs. After submitting, do not create the same task again just because nothing has come back yet — check the task status and the event log first. An external Agent that hits awaiting_approval must wait for you.

Results flow back

Finished images, videos, and audio belong in the media library, linked to the matching draft, subject, or project. A media task is only done when the file exists, the preview works, and it can still be found from the project.