Session-owned output
Private durable collections hold reusable variants without writing them into your checkout. Managed output is the default for delegated Designer work.
Swarming
Artifacts
Artifacts are durable outputs you can review, reuse, download, or bring into a workspace. They let a swarm return more than prose while keeping each result tied to the session and source that produced it.
Two output paths
Managed artifacts and workspace files solve different problems.
Ordinary project files
Files and packages live at explicit workspace paths. Use this path when the requested end product must be part of the repository or another workspace deliverable.
More than images
Managed artifacts can include text, Markdown, self-contained HTML, SVG, images, packages, and rendered MP4 files.
Linked to completion
Finished deliverables can appear in a session’s final handoff, preserving the exact ready artifact rather than duplicating its content.
Review in Desktop
Use the artifact sidebar and gallery for visual work.
Desktop automatically surfaces managed artifacts and iteration progress. You can inspect visual variants, compare results, select one into the conversation, download supported files or bundles, and open deliverables from final handoffs.
Self-contained HTML previews are sandboxed. Treat generated content as output to review, not as trusted application code.
TUI support today
The TUI can show artifact metadata, references, routes, tool activity, and final-handoff details. It does not yet provide Desktop’s rich gallery, visual preview, or comparison workflow. Open Desktop when you want to interact with generated artifacts visually.
Reuse and lineage
Select the exact source instead of starting over.
- Ask Swarm to search your owned artifact library when the source came from a prior session.
- Select an unambiguous ready variant and ask Swarm to reuse or remix that artifact.
- For a repository deliverable, ask Swarm to materialize the selected artifact into a trusted workspace path.
- Edit or transform the imported file normally, then publish the finished workspace result while preserving source lineage.
- Avoid downloading a preview and uploading it again when the original managed artifact is available.
Example
“Find the campaign image I approved last week, use that exact artifact as the source, preserve the subject and lighting, and create three tighter 16:9 crops.”
Beta status
The output is durable. The interaction model is still evolving.
Artifacts are in beta
Desktop currently provides the best review experience through its artifact sidebar and gallery. We are actively improving how you browse, compare, reuse, and organize artifact output. Please bear with us while we make this workflow truly great.
The beta label describes the browsing and review experience. It does not mean artifacts are disposable or that Swarm should silently lose source lineage.