docs: document shareable media artifact links and artifact media pages

src/content/docs/agents/capabilities/computer-use/artifacts-in-prs.mdx

@@ -23,7 +23,7 @@ Attachment is automatic: once a screenshot or recording artifact is associated w
 
 A team-level setting controls how artifacts are attached:
 
-* **Link only (default)** - Screenshots and recordings are attached as links to the run's page in the {VARS.WEB_APP}. Artifacts stay private: opening a link requires access to the run.
+* **Link only (default)** - Screenshots and recordings are attached as links to a media page in the {VARS.WEB_APP} that shows the single capture. Artifacts stay private: opening a link requires access to the run.
 * **Embed** - Screenshots render inline as images in the PR description, and recordings are attached as direct download links. To make this work, the attached artifacts are published at stable, publicly accessible URLs.
 * **Disabled** - No screenshots or recordings are attached to pull requests.
 
@@ -44,12 +44,27 @@ Team admins control the attachment mode from the [Admin Panel](https://app.warp.
 <figcaption>The Pull request artifact attachments setting in the Admin Panel.</figcaption>
 </figure>
 
+## Sharing captures outside pull requests
+
+A pull request isn't always where the evidence belongs. When an agent posts to Slack, comments on an issue or pull request, updates a Linear issue, or answers you in chat, it can pull shareable links for the screenshots and recordings the run captured and include the relevant ones in that message.
+
+Each link opens a media page in the {VARS.WEB_APP} that shows one capture — for example, `https://oz.warp.dev/artifacts/ARTIFACT_UID`, where `ARTIFACT_UID` identifies the screenshot or recording. Access is checked when the link is opened, so a link is safe to paste into an external tool: viewers who can't access the run are asked to sign in and are turned away if they lack permission.
+
+The team attachment mode applies here too:
+
+* **Link only (default)** - The agent gets media page links. Captures stay private.
+* **Embed** - The agent also gets direct image and video URLs, so screenshots and video thumbnails can render inline where the destination supports it. As in pull requests, those URLs are publicly accessible to anyone who has them.
+* **Disabled** - No links are available, and the agent reports that sharing is turned off for your team.
+
+To ask for this explicitly, tell the agent where the captures should go — for example, "post the screenshots to #eng-releases" or "reply with a link to the recording."
+
 ## Where else artifacts appear
 
 Pull requests aren't the only place captures end up:
 
 * **In the conversation** - Screenshots and recordings appear as blocks in the agent's conversation as they're captured.
 * **On the run page** - Open the run in the [{VARS.WEB_APP}](/platform/oz-web-app/#runs) to view, play, or download all artifacts the run produced.
+* **On a media page** - Every attached screenshot or recording also has its own page in the {VARS.WEB_APP} for viewing a single capture. See [Artifact media pages](/platform/oz-web-app/#artifact-media-pages).
 
 ## Related pages
 

src/content/docs/platform/oz-web-app.mdx

@@ -80,6 +80,12 @@ To start a new run:
 
 **Quick run** runs as your own user. A saved agent uses its saved defaults, and your prompt adds context for this particular execution.
 
+### Artifact media pages
+
+A screenshot or video recording an agent captured also has its own page at `/artifacts/<artifact-uid>`, showing that single capture with its description. Agents link to these pages when they attach captures to a pull request or share them in Slack, an issue comment, or a chat reply, so a reviewer can open one capture without opening the whole run.
+
+Access follows the artifact: private captures require signing in with an account that can access the run, while captures your team has published for embedding open without signing in. See [Screenshots and videos in pull requests](/agents/capabilities/computer-use/artifacts-in-prs/) for the team setting that controls this.
+
 ### Inspecting orchestrated runs
 
 The Oz web app renders [multi-agent orchestrations](/platform/orchestration/) as nested rows on the **Runs** page, so you can follow parent and child execution together.