product 1 Aug 2026 · 2 min read

Bring Your Documents to the Chat — and Take Them Away Again

Chat that only accepts images is chat you have to paste into. Files now go both ways. Sending files in Attach and ask in the same message. Supported today: PDF, Word, Excel, PowerPoint, CSV and TSV, JSON, XML, YAML, HTML…

ToRun Team ToRun Team

Chat that only accepts images is chat you have to paste into. Files now go both ways.

Sending files in

Attach and ask in the same message. Supported today: PDF, Word, Excel, PowerPoint, CSV and TSV, JSON, XML, YAML, HTML, Markdown, plain text, ZIP archives and a long list of source files — from JavaScript and Python to C#, Go, Rust, SQL and shell.

The text is extracted as you send, so the model answers about your document rather than about the filename. Spreadsheets come through as tables, so columns and headers survive instead of collapsing into a paragraph.

Two things we refused to fudge:

  • If your file is longer than the model you picked can read, you are told you are getting an answer about an excerpt. No confident summary of a document the model only half saw.
  • If a file cannot be read at all, it says so. It does not quietly ignore it and answer anyway.

Getting files out

Ask for a document and you get a document: xlsx, csv, docx, pptx, pdf, md, html, txt or json. "Turn this into a spreadsheet" produces a real spreadsheet, not a code block you have to paste somewhere. It lands in your Library like anything else you make, and you can ask to have it mailed to yourself.

This works in chat, on mobile and by voice. Long pastes now become a text attachment on their own rather than a message nobody can scroll past.

The changelog has the dated detail, including the limits.