Attach the input to the right conversation
In the September 8 development integration, supported room, thread, and direct-message paths carry attachment metadata to the agent. Send the file where the task lives and describe what the agent should do with it. Shared room mention rules still apply.
Receive a deliverable
A returned artifact belongs to the current task context. Hagency snapshots the output for durable delivery, and the client downloads it through the authenticated media path. A status message alone is not a file; check the actual attachment and expected content.
Handle encryption and recovery
Encrypted attachments need both authentication and the event’s encryption metadata. Recent native Robrix2 changes recover download behavior and avoid an indefinite spinner. Those changes were tested on the selected macOS development build.
If a download fails, retain the original conversation and device session, check media reachability, and retry through the client. A public media URL alone does not establish that encrypted content can be decoded.