Skip to main content
September 22, 2026 The Slack agent could already read images you shared. It now reads documents too, and can pass the original file through to Jira. Documents the agent can read Attach a file in a channel or a DM and the agent picks the first route that handles it:
  • Read directly: images, and plain text such as .txt, .md, .json and .xml, passed through as-is so JSON stays JSON.
  • Converted to markdown: .docx, .pptx, .xlsx, .xls, .csv, .pdf, .html and .epub, with spreadsheet tables and document headings preserved.
  • Skipped: anything else, or a file that fails to convert, with a thread reply naming the reason rather than silence.
Documents up to 10 MB are accepted, at most five per message, and converted content is not kept in the saved session history. Attaching a file to a Jira issue A PM filing a ticket from Slack usually has the spec in a spreadsheet, and that spreadsheet needs to travel with the ticket. The agent now has an attach_slack_file_to_jira_issue tool: ask it to create an issue and attach the file, and the original file lands on the issue, not the markdown the model read. It works on a later turn too, since the file id stays in the conversation, so “also attach that to KAN-4” does the right thing. The agent can only attach files shared in that conversation’s own channel, so a prompt cannot name a file it saw somewhere else. Agents that restrict tools with an allowlist need attach_slack_file_to_jira_issue added in the builder; agents with a denylist or no tool restrictions get it automatically. See Jira Tool and Starting a session. Shipped in Paradime v6.13.0.