Deliverable Mode for Native Chat Artifacts

Deliverable mode lets Hermes messaging gateways turn generated files into native chat attachments. The user receives an image, PDF, spreadsheet, audio file, video, or archive in the conversation rather than a path that exists only on the agent's machine.

Official documentation: https://hermes-agent.nousresearch.com/docs/user-guide/features/deliverable-mode

How delivery works

The agent creates a real file, verifies it, and mentions its absolute or home-relative path as normal text in the final response. The gateway recognizes supported extensions, removes the local path from the visible message, and uploads the file using the destination platform's attachment flow.

Paths inside code blocks or inline code are ignored. Source-code and log extensions are intentionally excluded from automatic delivery, so code examples remain code rather than surprise file uploads.

Artifact checklist

• Choose a format the recipient can use.
• Write the final artifact to a stable readable path.
• Open or parse the file before delivery.
• Verify dimensions, page count, rows, sheets, streams, or archive members as relevant.
• Mention the final path as plain response text.
• Keep internal drafts and private source files out of the response.
• Use a short human-facing caption that explains what is attached.
• Confirm the destination received the native attachment.

Kanban completion artifacts

Kanban workers can attach artifact paths to their completion record. When a subscribed completion notification is delivered through a supported gateway, those files can travel with the task summary. The task should still record what the artifact is and which verification passed.

Pitfalls

• Reporting a file before confirming it exists and opens.
• Mentioning a path inside backticks and expecting automatic upload.
• Sending a draft with the same name as the approved final.
• Delivering a chart without checking labels, crop, and readable scale.
• Treating gateway acceptance as proof that the recipient received the file.
• Shipping private source material merely because its extension is supported.

Verification steps

1. Generate a small public-safe test artifact.
2. Inspect its actual structure or media streams.
3. Send it to a dedicated test conversation through the real gateway.
4. Confirm the path disappears from the visible message.
5. Open the native attachment from the destination platform.
6. Compare the downloaded file with the local source.
7. Repeat with the production artifact only after the test path works.