Artifacts
Every file your agents produce, collected, viewable in-app, and publishable as revocable links.
"What did this agent actually make?" has one answer in Push: Artifacts — "Artifacts your agents produce — and files you ⌘-click in terminals — appear here."
Collecting
Files land in Artifacts two ways: an agent writes one during a run, or you ⌘-click a file path in any terminal pane. Each artifact stays connected to the issue and session that produced it, so the trail from "this file" back to "that conversation" never breaks.
Viewing
Artifacts open in Push's own viewer — markdown renders, images display, and hosted localhost servers (an agent's dev server, a generated web app) open right in the inspector pane instead of bouncing you to a browser. Two switches in Settings → Terminal control that behavior: "Open localhost links in the artifact inspector" and "Open pasted images in the artifact inspector." The per-tab inspector is ⌘I.
Utility actions on any artifact: Open in Finder, Copy Path, and Forget this artifact (removes it from the gallery without touching the file).
Publishing
Any artifact can become a public link: Copy Link publishes a snapshot and copies the URL — shown once, by design. Publish Again refreshes the snapshot after the file changed; Revoke Link kills it. The Published filter shows everything currently live, next to All Artifacts.
When you paste a live Push link into a chat or social app, its preview can show the artifact title and whether it is a shared file, terminal session, or session transcript. Push reads only that title and item kind for the preview; the file or session bytes stay on the separate content domain and render inside the isolated viewer. Revoked, expired, and unavailable links fall back to a generic preview. All share pages are excluded from search indexing.
Two honest notes on publishing, from How Push handles your data: a link exposes exactly the one item you published, on a separate content domain — and nothing publishes without you clicking the button. File publishing is additionally gated behind the human-only Allow file publishing switch in Settings → Workspace.