Skip to main content

Files And Workspaces

Each agent can have a filespace for attachments, reference material, generated outputs, and reusable working files.

Files covered by the installation's scanning policy can display Pending scan. The platform accepts the accompanying message text immediately, but protected file bytes cannot be opened, downloaded, sent, synchronized to a sandbox, or read by an agent until the malware scan is clean. A system administrator can disable scanning for specific source groups; those files can appear as Not required. A pending scan can persist during an outage. If a file is being replaced, the previous clean version remains available until the replacement is usable.

Ways files enter an agent workspace​

  • Chat attachments.
  • Email attachments.
  • Files uploaded through the file manager.
  • Files created by the platform during work.
  • Files handed off from a linked agent when peer messaging includes attachments.
  • Files referenced through Remote MCP or other supported integrations.

Chat attachments versus workspace files​

Use chat attachments for files needed by the current request.

Use the filespace when:

  • The file should be reused later.
  • The agent should reference it by name or path.
  • Multiple collaborators need access.
  • A generated output should remain available after the conversation scrolls.

Manage files​

Open the file manager:

  • hosted deployment: https://your-deployment.example/app/agents/<agent_id>/files/

From there you can upload, create folders, move files, download files, and delete files.

File status is durable and shown in the timeline and file manager. An infected file is destroyed and cannot be downloaded. A scanner outage leaves the file unavailable; a system administrator can retry it during the quarantine-retention window.

Good file practices​

  • Use descriptive names.
  • Organize recurring workflows into folders.
  • Remove stale files that could confuse the agent.
  • Tell the agent which file to use when multiple files are similar.
  • Avoid storing credentials or private keys as ordinary files.

Generated files​

When the platform creates a file, review it before sharing externally. For reports, exports, PDFs, charts, or images, ask the platform to include a concise summary in the timeline so collaborators know what changed.

Peer file handoffs​

When two agents are connected with Peer Linking, one agent can hand off an artifact to the other through a peer message. Ask the sending agent to attach or reference the specific file, and tell the receiving agent what to do with it.

Developer and MCP file use​

The Agent API and Remote MCP surfaces expose file-related behavior in different ways. Developers should see Agent API and Remote MCP.

Retention and long-lived files​

Organization files can be removed by retention policy. File eligibility uses creation time, so opening an old reference file does not extend its retention horizon. Before relying on a file for continuing work, check the policy and preserve a needed copy through the appropriate export or storage process.

Last updated on