“Create the document” should end with a document—not a wall of Markdown and a suggestion to copy it somewhere else.
Aii Cloud Work can now deliver two formats people actually pass around: Word documents and editable PowerPoint decks.
They share the same conversation and version history, but they take deliberately different paths.
From a report to Word
When you ask for a report, brief, proposal, or specification, Aii creates a complete Markdown artifact in the workspace. Markdown remains the durable source: easy to preview, diff, edit, and version.
Choose Download → Word (.docx) and Aii converts that artifact into a standards-based Word file in your browser. Headings, lists, tables, emphasis, and code blocks carry across. The converter does not send the document to a remote conversion service, and the generated package contains no macros, remote images, or external relationships.
You keep both options:
- download the original Markdown; or
- download the generated Word document.
If conversion fails, the source remains available. A binary download never replaces the artifact you can inspect.
Native PowerPoint, not HTML wearing a .pptx name
Presentations use a different pipeline. Ask Work to create a presentation, slide deck, or PowerPoint and Aii produces a real .pptx file with editable text and vector objects.
The workspace opens a slide navigator with previous/next controls, thumbnails, and a wide first-slide cover. The preview is generated from the deck's embedded, validated source and says plainly that fonts and rendering may vary in Microsoft PowerPoint. It is a useful layout preview, not a claim that a browser is Office.
Download returns the exact saved PPTX bytes. An externally edited or unrelated deck remains downloadable, but Aii will not fabricate a preview if it cannot verify the embedded source.
Revisions stay revisions
Follow up with a precise edit:
“Shorten slide three and make the final recommendation more direct.”
Aii creates a new version of the same presentation. The other slides remain, the previous download is still available, and selecting an older version scopes preview and download to that exact file.
The same model applies to documents: keep the source artifact, revise it in the conversation, and download the version you intend to send.
See the presentation loop: Open the Harbor Notes demo to compare the original two-slide deck with its five-slide revision and download either PPTX. The shared page also includes the Markdown brief; Word export is available from that source in the signed-in Aii Cloud workspace.
Share the conversation, not just the attachment
When you explicitly share a conversation containing a supported deliverable, the immutable file can travel with that snapshot. A reader can preview and download it. If they continue the conversation, their copy becomes independent under their own account and quota.
Unpublishing the original link revokes the shared page. It does not reach backward into files someone already downloaded or an independent continued copy.
Bring documents into the conversation too
The file picker can also read text from PDF, Word, Excel, and PowerPoint files in the browser. Extracted text becomes visible turn material so Chat or Work can summarize, compare, or transform it without requiring every selected model to natively understand Office formats.
Scanned PDFs without embedded text still need a vision-capable path. Styling, images, and complex layout are not silently presented as extracted text when only the words were available.
Try a complete document loop
Open Aii Cloud, choose Work, and ask:
Prepare an eight-slide board update from the attached quarterly notes.
Keep the design restrained, make the risks explicit, and end with the
three decisions the board needs to make.Review the deck, revise one slide, download the actual PowerPoint, and keep the conversation as the record of how it was made.
Word export is generated locally from the versioned Markdown artifact. Native PowerPoint creation produces a saved editable PPTX with a validated browser preview.