Files and attachment delivery
This page covers channel file inputs and outputs. The client must include attachment-delivery capability; a server prompt change cannot add transport support to an older client. Check installation and versions first.
Send materials to ClawPi
Send text, an image or a supported document in a paired conversation, with an instruction describing the task. Supported documents include PDF, DOCX, XLSX, PPTX, TXT, CSV, TSV and Markdown. Current client and platform size limits still apply.
Voice, video, quoted messages, archives, executable files and unsupported legacy Office formats are rejected rather than executed as ordinary tasks. Describe the goal again in a new message body when referring to earlier content.
Request an actual file
Specify the delivery format, for example:
根据刚才的待办清单，生成一个 PDF 文件并发到当前聊天。
文件名用“本周待办.pdf”，保留负责人和截止时间。Check for an actual attachment that opens in the phone or platform conversation, then inspect the corresponding desktop file card. A local path in a response does not mean a file was sent to the phone.
Sending a supported workspace file requires neither full access nor remote computer authorization. Screenshot delivery has separate rules; see Remote computer control.
Understand delivery status
| Desktop status | Meaning | Action |
|---|---|---|
| Pending / Sending | Preparing or submitting to the platform | Keep the client online and wait |
| Platform accepted | The platform accepted the request; it does not prove the recipient read it | Check and open the attachment in the source chat |
| Failed | Delivery did not complete successfully | Check the error and format, then explicitly request another send |
| Unknown | The submission outcome cannot be confirmed | Check the phone first to avoid duplicates, then decide whether to resend |
If the file is missing
Check that the task ran on a client supporting delivery, the conversation is still paired, the account is online and the format is supported. Prepared attachments resume from saved content; deleting the original workspace file does not cancel a prepared delivery.
Use a new message to explicitly request the same file again. ClawPi does not treat an unknown outcome as permission to retry indefinitely.