Skip to main content
Roomote can read supported file attachments from the web app and from chat threads where you start or continue a Roomote task. Support varies by chat provider. The web app, Slack, and Telegram can read the formats below. Discord supports images and a smaller text and code subset, but not Office documents, PDFs, or presentations. Microsoft Teams currently supports image attachments only. Slack can also describe one supported video attachment per message. Use attachments when the file itself is the fastest way to show the problem: a bug report export, a config file, a markdown handoff, a spreadsheet, or a PDF from a customer. Attachments work best when they are paired with a clear ask. Tell Roomote what the file is, which part matters, and what you want back: an explanation, a plan, a patch, or a follow-up question.

​
What works well

Attach files when you want Roomote to:
  • inspect structured data without pasting it into the message
  • read logs, config files, or source snippets as-is
  • work from a spreadsheet or report export
  • use screenshots and other images as direct visual context
If the attachments are large, Roomote reads them in the order you attach them and applies a shared text budget so the task stays responsive. Very large earlier files can leave later files included by name only. Text-extracted files are limited to 8 MB each. Image, video, and provider transport limits vary by surface.

​
Accepted file types

​
How Roomote uses them

Text, code, spreadsheet, document, and presentation files are read into the task as attachment context. Images are passed through as image inputs so Roomote can inspect them directly. .svg files are normally read as text markup, but Discord treats an SVG reported with the image/svg+xml content type as an image input. That means you can ask things like:
  • “Compare this export to the expected format and tell me what is broken.”
  • “Read this config and explain why the service is failing.”
  • “Check this customer PDF and draft the fix plan.”
  • “Look at this screenshot and tell me what UI state it shows.”

​
Best practices

  • Attach the smallest file that shows the issue clearly.
  • Add one sentence explaining what you want Roomote to do with the file.
  • Remove secrets or credentials before attaching files unless your deployment is explicitly configured to handle that material.
  • For spreadsheet or report exports, mention the tab, column, or row range that matters most.
  • For PDFs and documents, call out the section or page if you already know it.

​
Common issues

  • The attachment is huge. Trim it down or export just the relevant sheet, log window, or section. Text-extracted files larger than 8 MB are rejected.
  • The attachment is a format not listed here. Export it as one of the accepted formats above.
  • The task still needs more context. Add a short prompt that explains the question, expected behavior, or failure you want Roomote to investigate.