Artifacts are how Dokki produces interactive output — slides, dashboards, widgets, mini-apps. Most artifacts start as a Copilot prompt and get refined through chat.
Generate from a prompt
In any document, ask Copilot to make an artifact. The shape of the prompt determines the shape of the output:
Slide-style: "make a 5-slide pitch deck for our Q3 launch — title, problem, solution, demo, ask."
Dashboard: "build a dashboard showing this table as a bar chart and a KPI tile for total revenue."
Widget: "make a small embeddable widget that shows the current ETH price."
Quiz / interactive: "create a 5-question quiz about JavaScript closures."
Copilot generates the artifact, places it in the workspace, and returns a preview link in chat.
Iterate by chatting
Once the artifact exists, keep prompting:
"Make slide 3 darker."
"Swap the bar chart for a line chart."
"Add a question about hoisting."
"Use the data from the @Quarterly Numbers table."
Each iteration shows up live for collaborators.
Edit directly
Open the artifact in standalone mode to:
Tweak the content directly
Edit copy in place
Adjust styles or layout
Add custom interactivity
Direct edits and Copilot edits coexist — they merge automatically.
What artifacts can and can't do
Artifacts run in a safe environment inside Dokki. They can:
Render any UI you can build with HTML, CSS, and JavaScript
Use a curated set of libraries for charts, animations, and common helpers
They cannot:
Make arbitrary network requests outside an allowed list
Read other workspace data without your explicit grant
Run long background tasks
This keeps published artifacts safe for visitors and easy to embed.
Publishing artifacts
Like documents and tables, artifacts can be published — alone or as part of a workspace site. Visitors can interact with them, but they can't edit unless Public Access is set to edit.