Skip to content
Task 2.4 · 4 of 4

Share and discuss media

Everyone · Set up the workspace

1. Check what belongs in the channel before uploading

Media is stored on the relay like everything else, and it is readable by every member of the channel — agents included. A screen recording of a client's system, a photo of a whiteboard with client names on it, a contract PDF: all of these are the kind of thing that ends up in a channel by reflex during analysis work.

Apply the same test you would to a message. See Handle sensitive data where agents are present.

2. Upload the file

Paste, drag and drop, or attach the file to a message. Supported file types and size limits are not documented — test with your build before you depend on a particular format.

Since v0.5.20 the composer also has a GIF search (KLIPY). It only appears if the relay operator has enabled it: the relay proxies the search so the provider credential and your search terms go through the relay rather than from every client to a third party. In a client workspace, treat a GIF search that works as a sign the operator made that choice deliberately — and one that is missing as a choice, not a defect.

3. Comment on a video at a specific frame

Video comments can be anchored to a frame rather than left as a general remark. For analysis work this is the genuinely useful feature: a task recording can be annotated at the exact second where the performer hesitates, branches, or works around the system.

The exact interaction for creating a frame-anchored comment can vary between versions.

4. Point people and agents at the file

Reference the upload in the conversation so it is findable later. Search reaches file content in a permission-aware way, but a message that says what the recording shows saves everyone — including agents working in the channel — from having to infer it.

Verified against Buzz v0.5.20 · Updated 2 Sep 2026