The agent contract includes file-input configuration. This does not establish working image or PDF uploads, model processing, file retention, or per-file charging. Live multimodal conversation support is not available through this guide.
Prepare the input contract
The fields below belong toconversation_config.conversation.file_input and can be reviewed as part of an agent draft.
Prefer a small, explicit limit for your intended task. Do not interpret
-1 as an entitlement to unlimited storage or processing. These fields do not define a deletion schedule or establish how long files are retained.
Prepare examples for later testing
1
Define what the file contributes
Write one concrete task, such as identifying the model number on a product label. Specify what the agent should do when the label is unreadable or missing.
2
Select a compatible model when available
Check the current model catalog for the exact input capability. Text generation support alone does not establish image or document understanding.
3
Create a small review set
Use synthetic files covering a clear example, a low-quality example, an irrelevant file, and conflicting text. Record the expected answer and when the agent should request clarification.
4
Keep file input separate from knowledge
A per-conversation attachment is different from a maintained workspace knowledge document. Choose the latter for reviewed information intended to be reused across agents.
Frequently asked questions
Does enabled: true mean users can upload files now?
Does enabled: true mean users can upload files now?
No. It is an authored setting. A supported client, upload path, model integration, and released conversation path are still required.
Does the memory limit define file deletion?
Does the memory limit define file deletion?
No. Do not use these fields as a retention policy. Confirm the released file-storage and deletion behavior before accepting real user files.