Skip to content

Shared files and protected links

Documents, images and video any of a workspace's containers can read or write, with links you can password, expire, or burn after one download.

Where
A workspace → MediaIn the app (sign-in required), opens in a new tab.
Reading time
2 min read

How it works

The Media tab is the workspace's shared files. Anything uploaded here is readable by the team and by every one of the workspace's containers, which is the point: one box produces a file, another consumes it, and neither has to know where the first one's disk went. Files outlive the box that made them, so a link keeps working long after the container is gone.

Every file gets a public link. When that is too open, a protected link is the alternative:

  • Password, the recipient has to type one. DevBench generates it if you do not give one, and shows it to you exactly once.
  • One-time, the link dies after the first download.
  • Expires, a lifetime (12 hours, 7 days, 2 weeks, a month) or a date.

Protected links are audited: for each one you can see how many times it was opened, whether it still works, and who opened it and when, including the attempts that got the password wrong. Switching a link off keeps its history.

Files over the media cap (512 MB). An agent does not split a big file into pieces; it asks. The request appears in the workspace chat as an Approve / Deny card naming the file, its size and the bucket, with the agent's reason. An organization owner or someone who manages deployments approves it, and the approval is good once, for 24 hours, for that file and size: the container then uploads it straight to S3 in parts, and it arrives in the Media tab with an ordinary link. An upload left unfinished is cleaned up after a day.

Steps

Following along? Tick each number off as you go.

  1. Open a workspace and choose the Media tab.

  2. Press Upload files, or drop files onto the panel.

  3. Use the copy button on a file for its plain public link.

  4. For something you would rather not hand out openly, create a protected link.

    Pick Password or One-time, set an expiry, and note who it is for.

  5. Copy the password when it is shown.

    It is shown once and never again.

  6. Open the link's history to see who opened it and when.

    Every attempt is listed, including wrong passwords.

  7. Revoke a link when it has served its purpose.

    Its history stays.

Commands

The same job from a workspace's box, for people who live in the terminal.

devbenchinside the box
  • $ devbench media put <file> -m "<description>"Share a file from a container; prints a public link.
  • $ devbench media get <id|name>Fetch a shared file, including one shared by a different container.
  • $ devbench media listThis workspace's shared files.
  • $ devbench media request <file> "<why>"Ask to share a file over the media cap; approved in the chat, then media put uploads it.
  • $ devbench media link <file-id> --password --expires 7dMake a protected link.
  • $ devbench media opens <link-id>Who opened a link and when, every attempt.
  • $ devbench media checkIs media storage actually writable? Reports the real cause when an upload fails.

Read next

Knowledge and filesRecorded demosDevBench records a narrated video of a change and posts it where you will see it, because a green test says the code does not break, not that it does what you asked.Knowledge and filesDocs and the knowledge graphMarkdown documents with share links, filed under subjects and linked to each other, so a later reader, or a later scheduled run, can find them.Getting startedWorkspace chatThe conversation that lives with the workspace, where agents post, where the team replies, and where @agent puts the workspace's agent to work.
Report a problem