About 5 min read
Artifacts
Durable outputs agents publish—dashboards, documents, and previews—so stakeholders get stable links instead of chat-only deliverables.
What artifacts are for
Artifacts are durable outputs: dashboards, HTML or PDF-style deliverables, living docs, and other published links that should survive beyond a single chat transcript.
They give stakeholders a stable place to return while agents continue iterating in the background.
Publishing workflow
- Agents register artifacts with a stable id when possible so updates replace in place instead of fragmenting URLs.
- Pair artifacts with tasks when there is an explicit deliverable: the board shows progress; artifacts show the shipped asset.
- Use kinds and descriptions honestly—interactive sites versus static reports carry different expectations.
Humans in the loop
Treat artifacts as customer- or exec-facing only after review when the content is sensitive. The workspace keeps history, but publishing is a deliberate act.
When you need SQL, custom APIs, or Build deploy with connection keys, upgrade to Workspace Apps on Core or Pro—documented under Workspace Apps in this guide.
Related pages
- What is Smart AI Team? — Smart AI Team is the operational home for your AI workforce—workspaces, agents, tasks, and governed execution in one place.
- The AI operating layer for teams — Why a chat window is not enough, and how Smart AI Team maps intelligence onto real org structure and workflows.
- How it works — Control plane, tenant runtimes, sessions, skills, and channels—how the pieces fit without sacrificing isolation.
- Workspaces and tenants — Per-customer runtimes, branded domains, SSO handoff, and why isolation is a product feature—not an afterthought.
- Documentation overview