Agents

Document Author

The Document Author researches and writes a document or slide deck with you, inside a workspace. Describe what you want, watch it drafted into a live preview, keep asking for changes, and save the result into the workspace's Documents as Word, PowerPoint or Markdown.

The workspace authoring view: a chat with the Document Author on the left; on the right the file name, a PowerPoint (.pptx) format picker, the Trellaris (built-in) template, Save and Edit text above a live preview of the deck's slides.
Workspace β†’ Work β†’ Documents β†’ Author a document. The chat is on the left; the deck is drawn slide by slide on the right, in the chosen template, exactly as Save will build it.

At a glance

Handle@doc-author
AvailabilitySeeded in every organisation
Where you use itA workspace's Documents tab β€” Author a document, or Edit on an existing file
Model tierdefault
Autonomysupervised (the platform default β€” the definition declares none)
Toolswrite_canvas, web_search, web_fetch, market_data, currency_convert, calculate, current_time, generate_image, search_knowledge
KnowledgeThe knowledge of the workspace the document is written in (declared bare, no fixed collection)
Canvascanvas: single β€” one document per conversation
RoutableNo β€” routable: false. It is a surface you open, not a delegate the Orchestrator picks.

The authoring view

Open a workspace, go to Work β†’ Documents and choose Author a document. The page splits in two:

Gather first, then draft

A document is only as good as the facts in it, so the agent fetches them before it writes: web_search and web_fetch for anything current, market_data for prices and changes, search_knowledge for the workspace's own material (cited back to the passage), calculate and currency_convert for arithmetic, and current_time for today's date.

Documents and slide decks

Both are written as Markdown and built by the same code the preview uses, so what you see is what Save produces.

DocumentSlide deck
WhenReports, memos, proposals β€” anything read top to bottomYou ask for a presentation, deck, slides or PowerPoint
StructureOne # title, ## sections, paragraphs, lists, tables# is the title slide; each ## starts a slide of 3–6 one-line bullets
PreviewPagesNumbered slides at the template's aspect ratio, text shrunk to fit
Save As defaultWordPowerPoint

Templates

The template picker decides the look of the saved file. The default follows one rule: the workspace's chosen default for that format β†’ the first template uploaded to the workspace β†’ for PowerPoint, the built-in Trellaris 16:9 template β†’ otherwise plain formatting. Pick No template for plain output. The slide preview reads its colours, fonts and slide size from the template file itself, so an uploaded template previews exactly as it will save. Templates are uploaded, and defaults chosen, on the workspace Settings tab.

Charts, diagrams and images

Three ways to change it, cheapest first

  1. Edit in place

    Click a slide's title or a bullet in the preview and type, or use Edit text for the whole Markdown source. Your edit is saved as a revision and shown to the agent on its next turn, so the next instruction lands on your version.
  2. Quick edits, with no model call

    A few commands typed in the chat have exactly one right answer and apply instantly: replace "Q3" with "Q4", change the title to "FY27 plan", delete slide 4, delete the "Appendix" slide. Slide numbers are the ones the preview shows. Anything that does not match exactly goes to the agent rather than being guessed at.
  3. Ask the agent

    Everything else. The agent always has the whole current document (and, for a deck, the same numbered slide list you see), changes the part you mean and writes the complete document back, keeping the rest word for word. It never asks you to paste the document it is editing.

One document per conversation

The agent is declared canvas: single: every write revises the same document, and asking for a new title renames it rather than starting a second. Each document has one authoring conversation per person β€” reopen it later and you resume that conversation with its draft intact. These conversations belong to the document, so they do not clutter your chat list.

Saving and reopening

Why it is not routable routable: false means the Orchestrator will never delegate a step to it. That is deliberate: the Document Author is a workspace surface whose value is the live preview and the conversation around it, and a delegated child run has nobody watching. For "write me a document" in ordinary chat, the Assistant and Deep Research both carry generate_document and return a file.
Evaluating it An org admin can install the Document Author eval pack from Build β†’ Capabilities. Its cases check behaviour, not prose β€” for example that a request for current figures calls a research tool before the document is written (the tool_called assertion, read from the run's trace). See Playground.
It is a normal agent, so you can change it Every built-in is an ordinary org-ring registry agent with a versioned Agent.md. Edit it, publish a new version, roll back β€” the platform only re-publishes its own definition when you have not taken it over. See Build & promote.