• Features
• Media & Web
• Deliverable Mode

Deliverable Mode

When Hermes Agent runs inside a messaging gateway (Slack, Discord, Telegram, WhatsApp, Signal, etc.), it can deliver generated files directly into the chat — not as paths the user has to copy, but as native attachments.

A chart shows up as an inline image. A PDF report shows up as a file download. A spreadsheet uploads as.xlsx. The agent does not need to write aMEDIA:tag or do anything special — it just generates the file and mentions its absolute path in the response. The gateway picks the path out of the text, removes it from the visible message, and uploads the file natively.

.xlsx MEDIA:

How it works​

Three pieces fit together:

1. The agent has tools that produce files.execute_codefor charts via matplotlib, thelatex-pdf-reportskill for PDFs, thepowerpointskill for decks,image_generatefor images,text_to_speechfor audio, and so on.
2. The gateway scans agent responses for file paths.Any absolute path (/tmp/…) or home-relative path (~/…) ending in a supported extension gets extracted. Paths inside code blocks and inline code are ignored so code samples are never mutilated.
3. The gateway dispatches by file type.Images embed inline where the platform supports it; videos embed inline; audio routes to voice/audio attachments; everything else uploads as a file attachment.

The agent has tools that produce files.execute_codefor charts via matplotlib, thelatex-pdf-reportskill for PDFs, thepowerpointskill for decks,image_generatefor images,text_to_speechfor audio, and so on.

execute_code latex-pdf-report powerpoint image_generate text_to_speech

The gateway scans agent responses for file paths.Any absolute path (/tmp/…) or home-relative path (~/…) ending in a supported extension gets extracted. Paths inside code blocks and inline code are ignored so code samples are never mutilated.

/tmp/... ~/...

The gateway dispatches by file type.Images embed inline where the platform supports it; videos embed inline; audio routes to voice/audio attachments; everything else uploads as a file attachment.

Supported file extensions​

.png .jpg .jpeg .gif .webp .bmp .tiff .svg .mp4 .mov .avi .mkv .webm .mp3 .wav .ogg .m4a .flac .pdf .docx .doc .odt .rtf .txt .md .xlsx .xls .csv .tsv .json .xml .yaml .yml .pptx .ppt .odp .zip .tar .gz .tgz .bz2 .7z .html .htm

.py,.log, and other source-file extensions are intentionally excluded so the agent doesn’t auto-ship arbitrary source files; if you want to send code to the user, use a code block.

.py .log

Encouraging the agent to produce artifacts​

The agent doesn’t reach for artifacts by default — it has to know to. Two ways to nudge it:

Per-session:ask explicitly (“send me the comparison as a chart”, “return the data as a CSV”) or write your own custom-instructions / personality entry that biases toward artifact-style replies on messaging platforms.

Project-level:add the bias toAGENTS.md/CLAUDE.md/.cursorrulesin a project the agent works from, to your global persona in~/.hermes/SOUL.md, or as a named preset underagent.personalitiesin~/.hermes/config.yaml(switchable per session via/personality).

AGENTS.md CLAUDE.md .cursorrules ~/.hermes/SOUL.md agent.personalities ~/.hermes/config.yaml /personality

The mechanic the agent has to use is simple: render the file to an absolute path (e.g./tmp/q3-revenue.png) and mention that path as plain text in the reply. The gateway does the rest. Paths inside fenced code blocks or backticks are ignored so code samples are never mutilated.

/tmp/q3-revenue.png

Kanban: artifacts ride completion notifications​

If you use Hermes’ kanban multi-agent workflow, workers can attach deliverable files to theirkanban_completecall:

kanban_complete

kanban_complete(    summary="rendered Q3 revenue chart and report",    artifacts=[        "/tmp/q3-revenue.png",        "/tmp/q3-report.pdf",    ],)

When the gateway notifier delivers the “task completed” message to whoever subscribed to the task in Slack/Telegram/etc., it also uploads each artifact as a native attachment to that chat. The human gets the deliverable and the summary in one place.

Files that don’t exist on disk when the notifier runs are silently skipped.

Connecting more services with MCP​

Beyond the artifact-delivery pipeline, the agent can reach into other services via MCP (Model Context Protocol). The MCP ecosystem ships community servers for most popular tools — install whichever you need:

Install MCP servers via~/.hermes/config.yamlunder themcp_serverssection. SeeMCP integrationfor the full setup guide.

~/.hermes/config.yaml mcp_servers

Comparison to Perplexity Computer in Slack​

Perplexity Computer’s Slack integration is built around the same idea: the agent generates a deliverable (chart, PDF, slide deck) and posts it back into the thread as a native attachment. Hermes Agent’s deliverable mode provides the same user-facing pattern locally:

• Generation happens in the user’s own venv / sandbox (no remote tenant).
• Files land in the chat via the same Slackfiles.uploadV2API.
• Connector breadth comes via MCP rather than a curated catalog of 400 hosted integrations — install the ones you actually use.

files.uploadV2

OAuth tokens stay on the user’s machine inauth.json/.env. No hosted token storage. No multi-tenant microVM. Same end result.

auth.json .env