What counts as an Artifact
Artifacts are previewable outputs created during a session. Lumo recognizes formats such as Markdown, HTML, Mermaid, CSV, JSON, diff, SRT, directory trees, image comparison, content calendars, and cover-editor payloads.
Preview before you use it
The Artifact panel is meant for review. Markdown can be edited, CSV can be searched and sorted, Mermaid can be zoomed, SRT can be opened as subtitles, and content-calendar payloads can be checked before adding them to the calendar.
Library view
The Library view collects artifacts and sessions across work. It helps you return to useful outputs instead of hunting through old chats.
Auto-save behavior
When artifact auto-save is enabled, generated files are saved into an artifacts folder under the selected workspace. Interactive editors such as cover editing may still require manual export.
Use Artifacts as review points
A good Artifact should be easy to inspect without reading the entire chat. Open it when you need to compare versions, copy a finished section, check a calendar before import, inspect subtitles, or pass a previous result into the next task.
Reference previous outputs
When a previous output is still relevant, mention the Artifact instead of pasting everything back into the prompt. This is useful for asking Lumo to polish a script, generate metadata from a draft, create a cover from a brief, or split a transcript into short clips.
Keep names and folders readable
Use project names, dates, and platform labels in titles when possible. Saved Artifacts are easier to reuse when the folder tells you what the content package is, what platform it targets, and whether it is a draft or reviewed output.
When to move work into your own files
Keep early exploration in chat and Artifacts. Move the final script, subtitle, thumbnail export, or sponsor-facing note into your own production folder once it has passed review. This keeps Lumo useful for preparation while your publishing archive stays organized.