Artifact modes tell the agent what deliverable to create and which capabilities it needs. Choose a mode in the workspace, describe the result, and inspect the output in its artifact or editor pane. A completion message alone is not the deliverable.

​
Choose the format

Where the inline mode selector appears, its tabs stay on one horizontally scrollable row. The selected mode uses neutral glass with no accent color. Keyboard focus remains visible; reduced transparency and increased contrast use a solid selection surface. A missing tool, provider, or editor capability can block a mode. Choose an available runtime/provider or connect the required capability, then retry. The mode contract requires real output and tool evidence instead of simulated success.

​
Editor panes and bot threads

Docs, Sheets, Slides and PDFs work through artifact sessions with an editor pane. Subsequent turns edit the document already open in that pane. These sessions differ from a one-shot generation that emits a new artifact each time. PDFs open in the embedded PDF craft editor: the document saves back as a new version of the same artifact, and a read-only preview is available where the editor is not. Uploading a .pdf file to the workspace library also creates a PDF artifact. Images open in the embedded PhotoCraft editor: the layered source (.pcraft/PSD) is kept in the artifact’s runtime storage so edits keep their layers across sessions, and every save also writes a flattened image as a new artifact version — that flat image is what previews, shares and downloads show by default. “Download PSD” exports the layered source for use in other tools. Uploading an image file (PNG, JPEG, WebP, PSD, …) to the workspace library creates an editable image artifact. Videos open in the embedded FilmCraft editor: the footage is referenced from Allternit’s media storage (never copied into the artifact), the project source (.fcproj) is kept in the artifact’s runtime storage so edits keep their timeline across sessions, and every save also exports an MP4 that becomes the new artifact version — the export is what previews, shares and downloads play. Generated videos (media_generate) and uploaded video files (MP4, MOV, WebM) both land as editable video artifacts. On phones and the m.allternit.com PWA, a video artifact opens as the playable view first, with Edit video mounting the full editor for trimming and exports. Bot threads do not offer these three editor-pane modes. Use the workspace artifact session for the editable Office flow. A bot can still produce file deliverables through tools available to its thread; that is a different path from editing an open pane.

​
Inspect and continue

Keep the conversation for instructions and steering, and the artifact pane for the resulting work. Open a supported output to preview or edit it, check the contents, and ask for a specific revision. Available export formats depend on the artifact kind and the tool that created it. A thread’s artifact list and context checkpoint serve different purposes: the list collects outputs; the checkpoint preserves enough working context to continue. Review both when resuming a long task. See Artifacts API, Office suite, and Threads.