Files and attachments

Files are turn inputs and outputs, not bundle files. Aleph makes each attachment available only to the relevant turn.

Send a file#

Attach a file to a supported web or channel message. During the turn, the file appears under the sandbox's uploads/ directory. Tell the agent what you want it to do with the file instead of relying on the filename alone.

Discord accepts the slash command's optional file alongside its required message. Telegram accepts photos and documents with an optional caption or mention.

Receive a file#

An agent creates downloadable output by writing inside outbound/. Aleph starts each turn with an empty outbound directory and collects files after the agent finishes.

Channel delivery sends supported images as photos and other files as documents. Web conversations expose generated files with the assistant result.

Keep boundaries clear#

Attachments and ordinary workspace files do not become part of an immutable bundle and are not automatically durable memory. A sandbox path by itself is temporary, even when the runtime can briefly resume the workspace. If a file contains a fact worth remembering, the agent should save only the relevant durable knowledge—never credentials or an indiscriminate transcript. A file you need to receive must be written to outbound/ before the turn finishes.