[Feature]: Allow the bot to receive PDFs and be able to work with them

[omaralvarez]

Preflight Checklist

• I have searched existing requests and this hasn't been proposed yet
• If this request came from a chat session issue, I included relevant session context and redacted secrets

Problem statement

Whenever I send a PDF to Moltis through Telegram, it says it cannot find it locally. If I convert it to images it can process it fine. It would be awesome if Moltis could save the PDF locally and work with it or parse it to use it in the session. It would also be nice to be able to send PDF links apart from files.

Proposed solution

A receive attachment functionality, so whenever you send something through Telegram at least it is stored locally, so the agent can work with it.

Alternatives considered

Tested the sending PDFs converted to images and it works, but it is far from optimal.

Category

Channels (Telegram, Discord, etc.)

How important is this to your workflow?

Critical — blocking my use of Moltis

Additional context

No response

Chat session context (if applicable)

[penso]

This looks like it already landed on main.

I checked the git history and the core fix is in 93e4d5f9 (fix(telegram): persist inbound documents, 2026-04-12), with a follow-up in 9dcf0741 (fix(review): make inbound document replay robust, 2026-04-13).

What changed:

• Telegram document messages now download the file and persist it locally via save_inbound_document(...) before dispatching to chat (crates/telegram/src/handlers/implementation.rs).
• PDF uploads attempt text extraction, and the saved document metadata is attached to the user message so the agent can reference the local file path later.
• The agent-side message conversion now appends inbound document context, including the resolved local path, instead of relying on stale paths.

A few concrete references from main:

• crates/telegram/src/handlers/implementation.rs:360 saves inbound documents
• crates/telegram/src/handlers/implementation.rs:409 handles PDF extraction paths
• crates/telegram/src/handlers/media.rs:309 extracts PDF text
• crates/agents/src/model.rs:806 tests that inbound document context includes the local file path

So the main ask in this issue, receiving Telegram PDFs and making them available locally to the agent, appears to be fixed already. I’m closing this as resolved.

If you meant support for fetching and ingesting arbitrary PDF links sent in chat, that looks like a separate follow-up from the file-upload path covered here.