Artifacts & Deliverables
Artifacts are files that belong to an Anyy session: files you upload, media produced by a tool, or deliverables exported from the current Workspace.
Upload Files in Dashboard
In Dashboard → Chat, attach files before sending the message. One upload request accepts up to five non-empty files, each at most 50 MiB. The server stages them privately and binds only canonical artifact references to the message.
Tell Anyy what each file is and what outcome you want:
Use the attached CSV and notes to create a concise Markdown report with a comparison table. Return the report as a downloadable file.
Wait until each upload finishes before sending. A staged upload is not yet part of conversation history; sending binds it to that session. A filename or an artifact:// reference by itself does not grant another session access.
Create a Deliverable
Anyy can use file, terminal, Skill, or other enabled tools to write a result inside the current Workspace. To deliver it, Anyy uses artifact_export rather than returning a local filesystem path.
The export accepts only a Workspace-relative path. Absolute paths and .. traversal are rejected. An optional filename changes what you see in the attachment; it does not select a different source file. The source must be a regular file under the Workspace. Exporting a file that changes while being copied fails, so finish writing the deliverable before asking Anyy to attach it.
Export Limits
An exported Workspace file must be at most 50 MiB. The generated attachment expires after 24 hours unless another supported artifact workflow pins or preserves it.
Export saves a separate durable copy of the bytes and records a scoped reference for the response. Conversation history stores that reference and attachment metadata, rather than depending on the original Workspace path or a temporary provider URL. If export fails, the original Workspace source is left untouched so Anyy can correct the problem and retry.
Say “return it as an attachment” or “give me the downloadable file.” This tells Anyy that a path printed in chat is not the finished deliverable.
Inspect Existing Artifacts
Within the current session, Anyy can list active artifacts, inspect supported image/video artifacts with a configured model, and pin an artifact where the product surface supports it. PDFs and documents are handled through their manifest/file paths and suitable file or Skill tools rather than the image/video inspector.
Ask in the same session, for example:
List the active artifacts in this conversation, then inspect the chart image again for changes in the final quarter.
Pin artifact ARTIFACT_REF so normal retention cleanup keeps it.
Pin while the artifact is still available. Pinning removes its normal expiry; it does not restore an already expired or missing file. Keep a downloaded copy or Profile backup when the file matters.
Artifact references are scoped to their owning Profile and session context. A reference from another session is not automatically available in the current one.
Files and model context
Keeping a file is different from keeping its full contents in every model request. Anyy includes bounded artifact manifests and scoped references in context. Older images and videos are not automatically re-embedded on every turn; ask Anyy to inspect an available artifact again when its visual details matter. A successful file export does not prove that its contents fit the current model’s context or that a particular Channel supports them.
Delivery to Channels
Dashboard can present the attachment directly. A messaging channel can deliver it only when that adapter supports the file's media kind and size. If a channel cannot deliver it, open the same session in Dashboard.
Privacy and Retention
- Uploaded and generated files are Profile data.
- A model or tool provider may receive the file when the requested operation requires it.
- Unsent staged Dashboard uploads expire after 24 hours.
- Delete or back up Profile data according to your retention needs.
Troubleshooting
| Symptom | Check |
|---|---|
| Anyy returns only a local path | Ask it to export the Workspace-relative file as an attachment |
| Export rejects the path | Move the file under the current Workspace and avoid absolute/parent paths |
| File is too large | Reduce it below 50 MiB or split the deliverable |
| Attachment expired | Regenerate or re-export the source file |
| Channel cannot receive it | Download from Dashboard or choose a supported media kind/size |