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.
| Aspect | Static Artifact | Live Artifact |
|---|---|---|
| Data source | Hardcoded content | Connector-backed (Notion, databases, APIs) |
| Updates | Manual regeneration | On-demand or scheduled refresh |
| Versioning | Conversation-based | Refresh log with delta tracking |
| Failure recovery | N/A | Staleness detection + retry |
How Live Artifacts Work
Creation
- The agent produces an artifact that references connector data sources.
- The live-artifacts subsystem registers the artifact with its data dependencies.
- A
manifestis stored linking the artifact to its connectors.
Refresh
- Trigger — manual refresh button or scheduled refresh.
- Fetch — the refresh service calls each connected data source.
- Re-render — the agent updates the artifact with fresh data.
- Persist — the new version is stored with a refresh log entry.
- 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:
| Endpoint | Method | Description |
|---|---|---|
/api/live-artifacts | GET / POST | List or create live artifacts |
/api/live-artifacts/:artifactId | GET / PATCH / DELETE | Manage a specific artifact |
/api/live-artifacts/:artifactId/preview | GET | Preview the rendered artifact |
/api/live-artifacts/:artifactId/refreshes | GET | List refresh history |
/api/live-artifacts/:artifactId/refresh | POST | Trigger a manual refresh |
/api/tools/live-artifacts/create | POST | Agent-facing: create a live artifact |
/api/tools/live-artifacts/list | GET | Agent-facing: list live artifacts |
/api/tools/live-artifacts/update | POST | Agent-facing: update an artifact |
/api/tools/live-artifacts/refresh | POST | Agent-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.