Skip to main content

Live Artifacts

Live artifacts are a powerful TF Design feature that lets the agent produce refreshable, data-backed artifacts. Unlike static prototypes and decks, live artifacts connect to external data sources and update on demand or on a schedule.

What Makes an Artifact "Live"​

A live artifact is an HTML artifact backed by one or more connector data sources. When refreshed, the agent re-fetches data from connected sources, re-renders the artifact with updated values, and produces a new version — all without re-running the full generation pipeline.

AspectStatic ArtifactLive Artifact
Data sourceHardcoded contentConnector-backed (Notion, databases, APIs)
UpdatesManual regenerationOn-demand or scheduled refresh
VersioningConversation-basedRefresh log with delta tracking
Failure recoveryN/AStaleness detection + retry

How Live Artifacts Work​

Creation​

  1. The agent produces an artifact that references connector data sources.
  2. The live-artifacts subsystem registers the artifact with its data dependencies.
  3. A manifest is stored linking the artifact to its connectors.

Refresh​

  1. Trigger — manual refresh button or scheduled refresh.
  2. Fetch — the refresh service calls each connected data source.
  3. Re-render — the agent updates the artifact with fresh data.
  4. Persist — the new version is stored with a refresh log entry.
  5. Display — the preview updates to show the latest version.

Failure Handling​

  • Staleness detection — if a refresh fails, the artifact is marked stale.
  • Abort handling — in-progress refreshes can be aborted.
  • Refresh locks — prevents concurrent refreshes of the same artifact.
  • Retry — stale artifacts can be manually retried.

Internal Endpoints​

The following endpoints are exposed by the running Desktop app's embedded runtime for in-app tools and the agent:

EndpointMethodDescription
/api/live-artifactsGET / POSTList or create live artifacts
/api/live-artifacts/:artifactIdGET / PATCH / DELETEManage a specific artifact
/api/live-artifacts/:artifactId/previewGETPreview the rendered artifact
/api/live-artifacts/:artifactId/refreshesGETList refresh history
/api/live-artifacts/:artifactId/refreshPOSTTrigger a manual refresh
/api/tools/live-artifacts/createPOSTAgent-facing: create a live artifact
/api/tools/live-artifacts/listGETAgent-facing: list live artifacts
/api/tools/live-artifacts/updatePOSTAgent-facing: update an artifact
/api/tools/live-artifacts/refreshPOSTAgent-facing: trigger refresh

Use Cases​

  • Sales dashboards — auto-refresh from CRM connector data.
  • Team status boards — pull from project management tools.
  • Financial reports — update with latest accounting connector data.
  • Live charts — re-render with fresh metrics from monitoring APIs.
  • Inventory grids — reflect current stock levels from e-commerce connectors.

Configuring Live Artifacts​

Live artifacts require at least one configured connector. See Connectors for setup details. The agent determines which data sources to use based on the brief and available connectors.