CapabilitiesFiles and outputs

Files and outputs

Blazing Agents separates durable private work from files an application should receive. Attach a Sandbox when an Agent needs a persistent workspace, enable file Tools to operate in it, and publish selected files as Artifacts only when they are ready to leave that workspace.

Choose a file capability

CapabilityPurposeOwnerPersistenceVisibilityCreated by
SandboxProvide durable workspace and compute for file ToolsTenant; attachable to at most one AgentUntil the Sandbox is deletedPrivate execution environmentTenant through the SDK or REST API
File operationsRead, write, edit, search, and run commands in the workspaceOperate on the attached SandboxFiles remain until changed or the Sandbox is deletedPrivate to the Sandbox data planeAgent Tool calls during a Turn
ArtifactDeliver a selected file as an application outputTenant, Agent, and Session, with Session AttributionImmutable until deleted; the record is then tombstonedDownloadable through the authenticated SDK or REST APIAgent through save_artifacts

A workspace file is not an Artifact. Scratch files remain private even after a successful Turn unless the Agent explicitly publishes them.

From workspace to output

The complete path is:

  1. Attach a Sandbox to the Agent.
  2. Enable the Sandbox-backed file Tool group.
  3. Let the Agent create and revise files in the workspace.
  4. Ask the Agent to publish selected paths with save_artifacts.
  5. List and download the resulting Artifacts through the SDK or REST API.

Publication is optional. A coding or analysis workflow can keep durable files for later Turns without creating any Artifacts.

Explore file capabilities

Reference

On this page