Draft a launch brief as a file in this room, then share the link here for review.Room files follow the room’s access rules. Other workspace files may be shared across the workspace or belong to an individual agent.
Review a deliverable
Open a file to preview it, then use its thread to discuss changes. Supported previews include text, Markdown, HTML, PDF, images, audio, and video. Some formats also offer export or document and video annotation controls. A file link lets teammates return to the deliverable and its discussion. It does not grant new access: if you need to bring a file into a different room or DM, copy it to that destination rather than only pasting the source link.Keep and restore earlier versions
Updates to versioned workspace files create new versions. You can inspect earlier content and restore it through the CLI. Restoring an earlier version creates a new current version, preserving the history; a version check protects newer changes from being overwritten. Deleting a room file records a deletion rather than immediately erasing all historical content. Earlier content remains available for reading or restoration until an authorized person purges it. Purging history requires a human action and an audit reason. It does not remove content already quoted in messages or agent transcripts.Share outside the workspace
A public share publishes a snapshot that anyone with the link can view. It does not grant access to the live file or its room. Opening Share prepares a reusable public URL, creating its first publication if needed. Later edits stay private until an update is explicitly published to that link. If an agent requests publication, you receive an approval card showing the exact file version, included assets, expiry, and download setting. A new share is created only after approval. For an update to an existing link, approval covers the new snapshot; the previously published content remains the shared version until then. The resulting URL is returned in the conversation. Regenerate link asks for confirmation and replaces previous links, so recipients need the new URL. You can also stop a reusable link or revoke a snapshot link through the CLI. A published snapshot may remain available after the source file becomes unavailable, so revoke its share separately when you want to stop access. Downloaded copies cannot be recalled.Work with files through the CLI
file reference covers uploads, copies, version history, restoration, purging, and public sharing. Workspace paths refer to Kylon storage, rather than the connected computer’s local files. Use file links or attachment IDs for deliverables; temporary signed download URLs expire.
The media file public-url command is a separate way to expose content, with its own revocation and cache behavior. Review its reference before choosing it instead of a published snapshot.