Files and attachments

Send source material

Attach files to explain the task or provide material Amazi should use. The composer supports file selection, drag-and-drop, and paste. Tell Amazi whether the file is a reference to read, an asset to place in the application, or source code to import.

To reuse a file already sent in this project, mention its filename or reply to the original message. Amazi can retrieve the existing attachment. If it uses an incorrect file reference, it receives guidance to correct that reference; you do not need to upload the same file again for that reason.

After reading or saving a file, Amazi may still need time to examine its contents, update the application, and verify the result. Follow the work summary for progress; a completed file operation does not mean the whole request has finished.

Files in queued messages appear inside the message bubble with their names, sizes, and image thumbnails. You can preview images and text files or download other files before the message is sent.

Images stay in the attachment carousel. If the message field has focus when you add an image, a chip with its filename is also inserted at the caret. Adding an image without focus does not change the message text.

In project chat, type @ and choose Attachments, the first menu item, to insert a reference to an already attached image. Filter by filename and select the image. Clicking its chip opens the image editor; removing the chip keeps the file attached. Removing the file from the carousel also removes its chips. References remain available when a draft is restored or a queued message is edited.

An uploaded archive is not automatically a running application. Importing it may require extracting files, identifying the framework, installing dependencies, and configuring its startup behavior. Ask explicitly if you want the source added to the project.

In a sent message, clicking an image chip opens the same viewer as clicking its file in the attachment carousel. Files attached to an answer to Amazi's question are delivered with that answer; you do not need to attach them again as a separate chat message.

Upload limits

One user submission accepts up to 10 files, with a combined limit of 50,000,000 bytes. A single file cannot exceed that limit. If a selection exceeds the limit, correct the selection before sending it.

For larger files, use direct upload in Code or a connected-device transfer. You can also provide a direct HTTP or HTTPS download link that Amazi can access. A file-sharing page that requires an interactive login is not necessarily a direct download link. Do not send your account password to make it accessible.

Ask for a downloadable result

You can request an artifact directly:

Turn the attached notes into a Word document and attach the finished file. Do not create an application.

Amazi can attach files produced in the project workspace. An application is not required just to deliver a document. Reply attachments support up to 10 files, each at most 50 MB; generated images count toward the reply selection too.

A path printed in a message is not itself a downloadable attachment. Use the attachment card supplied with the answer. If the expected file is missing, ask Amazi to attach the existing result rather than regenerate it unnecessarily.

Know what has been saved

Reading an attachment does not automatically copy it into application source. Large text files, such as XML configurations, may need to be saved in the project and searched or parsed in smaller sections. The original file is preserved. Support may ask for a smaller relevant excerpt because it cannot save files. Likewise, attaching a generated file does not prove that it was integrated into a page. State whether you want a download, application integration, or both.

Keep secrets out of uploaded examples. Prefer synthetic data for analysis and testing. For persistent files uploaded by your application's users, use Database and storage, not chat attachments.

Upload directly into the project

In Code, open a folder's context menu and choose Upload files, or use supported drag-and-drop into the file tree. This stores files in the project workspace without sending them as chat attachments. One selection accepts at most 100 files, 1 GB per file, and 10 GB total. Archive larger file counts before uploading. An archive stays an archive: upload does not extract it, import its source, or add ignore rules. Existing names are not overwritten. Successful changes enter project file history. Use a direct download link or direct project upload when the chat's 50 MB limit is too small. Tell the agent the uploaded path and what to do with it.