Everything Okou produces — presentations, websites, images, videos, reports, files — collects in the Artifacts section in the sidebar. It's there so a deliverable doesn't get buried in the conversation that created it.
What lands there
Anything a run generates as a file or a shareable output:
- Decks, reports, posters, and dashboards from the built-in generation pipelines
- Images and illustrations
- Videos, including talking-avatar videos, and voice audio
- Websites and other HTML bundles, before or after you publish them
- Files a run downloaded, converted, or exported
Artifacts are grouped by type, so "find that deck from last month" doesn't mean remembering which chat produced it. Opening one takes you back to its conversation when you need the context around it.
Why it exists
The alternative is scrolling. A chat that ran for forty steps and produced six files is a bad filing system — you remember the artifact, not the thread that made it. Artifacts inverts that: start from the thing you're looking for.
It matters most for two patterns:
- Recurring automations. A weekly report produced by an automation piles up in one automation chat. Artifacts lets you pull last week's without scrolling past this week's.
- Media work. Image and video runs produce variations. Comparing them side by side is easier from one place than from six points in a conversation.
Delivery is still separate
An artifact in the sidebar is yours. It isn't published, sent, or shared until you say so:
- To give someone a link, publish it as a hosted site.
- To put it in a channel or an inbox, name the destination in your request — see Integrations.
- To keep a copy, download the file.
What's next
- See Generation for producing artifacts in the first place.
- See Hosted sites for turning HTML output into a URL.