<!-- description: An attachment is a file or binary payload sent alongside an agent task or message, allowing agents and humans to share screenshots, logs, diffs, and other artifacts during collaboration. -->

# Attachment

An **attachment** is a file or binary payload associated with an agent [task](task) or message. Attachments let AI agents and humans share artifacts — screenshots, log files, diffs, error reports, or any other binary content — as part of their collaboration workflow.

## Why Attachments Matter

Text alone is often insufficient for agent-human collaboration. An agent might need to:

- Share a screenshot of a UI bug it discovered
- Attach a log file that explains a crash
- Send a diff of proposed code changes for review
- Upload a generated report or export

Attachments bridge the gap between the agent's work environment and the human reviewer.

## Attachments in AgentRQ

AgentRQ supports attachments on tasks and messages. When a [Claude Code](claude-code) agent calls the AgentRQ [MCP](mcp) tool, it can include file references that are uploaded and made available for download on your [task board](task-board).

To download an attachment, use the `downloadAttachment` MCP tool, which returns the binary content of the file by its ID.

## Common Attachment Types

- **Screenshots** — visual proof of UI state or test failures
- **Log files** — raw output from builds, tests, or deployments
- **Diffs / patches** — proposed code changes for human review
- **Reports** — structured summaries generated by the agent
- **Config files** — proposed configuration changes awaiting approval

## Related Terms

- [Task](task)
- [Bidirectional Messaging](bidirectional-messaging)
- [Approval](approval)
- [MCP Tool](mcp-tool)