Documentation feedback

Help us improve this page.

About

We use submissions to improve Swarm and may reply if you include an email. Human verification is required. See our Privacy Policy.

Swarming

Artifacts

Artifacts are durable, version-controlled project deliverables you can inspect, review, download, or bring into a workspace. Powered by the Git-backed Artifact V3 architecture, artifacts let Swarm build rich visual documents, interactive applications, vector animations, and media while preserving full commit history and source lineage.

Two output paths

Managed artifacts and workspace files solve different problems.

Managed

Session-owned output

Private durable collections hold reusable variants without cluttering your checkout. Managed output is the default for delegated Designer and media work.

Workspace

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.

Formats

Multi-file projects

Managed artifacts can be standalone HTML, CSS, JavaScript, SVG, Markdown, multi-file packages, images, audio, or rendered MP4 video files.

Handoffs

Linked to completion

Finished deliverables appear directly in a session’s final handoff card, preserving the exact ready artifact rather than duplicating raw text.

Artifact V3 Git architecture

Every artifact is an internal Git repository with immutable commits.

Artifact V3 (swarm.artifact/v3) transitions artifact generation from fragile monolithic text replacement into true version control. Each artifact lives as an internal Git repository with full tree storage, surgical file edits, and safe concurrency.

  • Immutable commits and branches: Every generation turn commits changes into Git. Parallel candidate options live on isolated branches before selection.
  • CAS-guarded HEAD pointer: Switching the active visual head uses Compare-And-Swap (CAS) pointers (select_v3), eliminating race conditions between concurrent agents or human edits.
  • Surgical draft operations: Agents manipulate files incrementally using read_file, edit_file, and build_preview before calling finish_turn. This prevents full-file wiping and retains precision.
  • Resumable drafts: If a draft build fails, Swarm inspects the diagnostics and resumes editing the existing working tree rather than regenerating from scratch.
Multi-part compositions

Artifacts define structured Parts (such as selector, temporal, spatial, or semantic targets). Parts express focused user intent and visual components without splitting files into disconnected pieces.

Desktop Artifact Studio

An IDE-grade visual workspace built into Swarm Desktop.

Desktop Artifact Studio provides an interactive visual workbench for inspecting, navigating, and debugging generated artifacts.

Navigation

Rounds & Options

Browse through iteration turns and candidate variations with instant visual diffs and revision history.

Bi-Directional Sync

Parts Navigator

Click any element in the sandboxed preview iframe to highlight its declared Part and source code in the inspector.

Timeline Control

Animation Scrubber

Scrub frame-by-frame through complex CSS, SVG, or Three.js animations with pause, step, and playback rate controls.

Diagnostic Loop

One-Click Repair

If an artifact encounters runtime errors, click Repair with Swarm to feed console diagnostics and stack traces directly into an automated repair run.

Scene contracts and profiles

Deterministic animation execution with strict performance budgets.

To prevent browser freezes, frame drops, and runaway animation loops, Swarm enforces declared scene contracts and pinned animation profiles.

Profile 01

motion_ui

Standard CSS keyframes, Web Animations API (WAAPI), SVG motion, and lightweight 2D Canvas components.

Profile 02

spatial_3d

Three.js and WebGL scenes resolved via pinned local import maps without external CDN dependencies.

Profile 03

vector_playback

Licensed vector animations including dotLottie and Rive runtimes for interactive UI illustrations.

Profile 04

final_render

Video rendering targets that deliver deterministic MP4 playback assets for production deployments.

Scene contracts

Multi-scene animations declare a strict scene_contract specifying total duration_ms and contiguous, non-overlapping scene boundaries. Swarm guarantees smooth timeline transitions between all chapters.

Exporting stills and MP4s

Headless Chromium capture turns web artifacts into media assets.

Swarm can render and export web-native artifacts directly into production-ready static images or video files without manual screen recording.

  • Stills export (export_html_stills): Captures pixel-perfect 1920×1080 PNG screenshots of declared visual states or keyframes.
  • Animation export (export_html_animation): Steps through an animation’s seek(time_ms) method frame-by-frame, encoding a perfectly paced, drop-free H.264 MP4 video.
  • Fallback rendering: If an animation lacks deterministic seek controls, Swarm uses timed real-time window capture to preserve motion.
  • Direct Video Studio import: Exported MP4s or live HTML animations can be pulled straight into Video Studio timeline tracks via convert_artifact_v3.

Reuse and lineage

Select the exact source instead of starting over.

  • Ask Swarm to search your owned artifact library when a source was created in an earlier session.
  • Select an unambiguous ready variant and ask Swarm to remix or extend that specific revision.
  • For a repository deliverable, ask Swarm to materialize the selected artifact into a clean workspace path.
  • Edit or transform the imported files normally, then publish the finished workspace result while preserving Git commit lineage.
  • Avoid downloading previews manually and re-uploading them; managed references preserve the full origin chain.
Example

“Find the 3D particle visualization artifact I approved yesterday, use that exact revision as the source, and export a 1080p MP4 animation of the first 8 seconds.”