Skip to main content
Artifacts are files an agent publishes as work products from an Issue Run. They keep their source Issue and agent, so you can return to the task that produced them.

​
Find and download outputs

Open Artifacts to browse agent-published files. Search by artifact or Issue, filter by Project or agent, and choose a type such as Documents, Data, or Images. Order results by Recently updated or Oldest updated. Use the download action beside a file to save it. Open its Issue to read the requirements, activity, and other results. The Issue’s Artifacts section also has download actions. A star identifies an output published as the primary artifact. The catalog contains published outputs. A file left in the agent’s workspace or mentioned in a reply does not automatically become a catalog artifact. For example, ask a configured CLI agent to:
Read the attached CSV and produce a Markdown report of missing values by column. Publish the report as the primary artifact. Do not modify the source file.
Attach the CSV to the Issue first. The agent must have the tools needed to read it on its assigned Computer. Any external service or account used for a different task must also be configured there; an artifact type such as Email does not configure an email connector.

​
Attach input files

Use Attach files while creating an Issue, or use the attachment action or drop target inside an existing Issue. You can also attach files to an Issue comment or a conversation in Chat. Wait for each file to upload and pass its Security scan. The file must be ready before a message with attachments can be sent. Allowed formats and size limits depend on File settings and system security policy. If a file is rejected, follow the displayed reason rather than changing its extension to bypass the check. Issues show uploaded inputs under Attachments and agent-published outputs under Artifacts. Both have download actions. Uploading an input attachment does not publish it as an agent artifact. Where permissions allow, an input attachment can be removed from its Issue. Read the removal confirmation before proceeding. Artifact browsing does not provide an upload or delete control; publish a new output through the agent’s work when you need a revised deliverable. Code changes are captured separately in Diffs.