Documents, reports & print-ready output
Most agent output dies in the chat window. Sonderr's does not: writing happens as artifacts — real files on your machine, previewed in the artifact panel, delivered as download cards. This guide covers the whole writing path, from a one-paragraph summary to a print-ready document, including the formats the panel renders and the quality bar for a report that survives review.
Writing is the most common deliverable an agent produces, and the most commonly mishandled: a wall of chat text cannot be filed, printed or shared. Sonderr treats every document as an artifact — a real file on disk, shown in chat as a download card and previewed in the artifact panel. If it matters, it is a file; if it is a file, you can download it, move it and keep it. The mechanics of cards and the panel are in Artifacts, files & deliverables; this guide is about making the writing itself good.
1 · From prompt to document
A writing task needs the same four-part brief as any other: outcome (what the document must achieve), audience (who reads it), constraints (length, tone, format, hard requirements), references (style or prior documents). Ask for the file explicitly — "as a markdown file" or "as HTML I can print" — so the deliverable lands as an artifact rather than chat prose. For anything with structure, one extra sentence saves three rounds: "give me a one-page summary, then the detail below it."
2 · What the artifact panel renders
| You produce | The panel shows | Good to know |
|---|---|---|
| Markdown | Rendered markdown, styled | Copy and download in the header; ESC closes. |
| Code | Syntax-styled source | Line-faithful; copy keeps it exact. |
| JSON | Pretty-printed tree | Still valid JSON when copied. |
| CSV / TSV | A real table | Headers respected; large files scroll. |
| Images | Preview on a checkerboard | Generated or uploaded alike. |
| Binaries | Download-first | Never garbled into "readable" text. |
3 · The print-ready recipe
When the deliverable is paper — a report to hand in, a one-pager to pin up — Sonderr has a dedicated workflow from the recipes library: produce the document as clean HTML or markdown, apply the print styles, and check it against the brief's constraints (page count, margins, fonts) before delivery. The pattern is spelled out in Recipes — eight real-world workflows. The two rules that matter most: separate content from layout (let the agent fix one without touching the other) and print-preview before accepting (the panel preview and the printed page agree only if you check).
4 · Reports that survive review
A report is writing with opponents — readers who will check the numbers. Three habits make Sonderr's reports defensible. First, claims carry evidence: every non-obvious statement points at the data, file or source it came from. Second, uncertainty is labeled: "measured", "estimated" and "assumed" are different words and the report uses them differently. Third, structure mirrors the decision: summary first, detail after, appendix last — so a skeptical reader can audit from the top without hunting. If the report draws on live sources, the honesty rules in Research that holds up apply unchanged.
5 · Long documents without losing the thread
For anything over a few pages, treat it as a project: plan the sections in Plan mode, then let Build produce section by section with the task list tracking progress. Long work writes checkpoints — covered in Marathon tasks — so a session crash costs a section, not the document. The craft-with-a-definition-of-done version of this workflow, including document-specfics like milestone slices per section, lives in Studios — goal to deliverable.
One honest note to close: the artifact panel previews markdown, code, JSON, CSV/TSV and images — it is not a word processor, and it does not render proprietary desktop formats. If a format you need is not on the list, the artifact is still delivered as a file; download it and open it in the tool that owns the format.