Unified Workspace

One File System. Every Capability. Seamless Workflows.

A session-scoped file system where Files, Sandbox, Code Runner, and WASM plugins all access the same storage — enabling true multi-tool collaboration.

Shared File Access

What is the Unified Workspace?

A session-isolated file system accessible to every capability type

Every agent session gets its own isolated workspace backed by cloud object storage. Built-in capabilities (Files, Sandbox, Code Runner, Computer) and WASM plugins all directly access the same storage.

/workspace/input/

Read-only

User uploads and session context files. All capabilities can read from here.

/workspace/output/

Read-Write

Agent-generated results and artifacts. Quota-enforced with per-file size and file count limits.

No data copying. No context switching. Every capability reads and writes the same files.

Universal Access

How Every Capability Connects

Built-in tools, containers, and plugins — one shared workspace

Files

11 MCP tools for direct file operations — ls, read, write, copy, move, delete, mkdir, stat, exists, and append.

Sandbox

Linux containers with workspace mounted as native volumes. Run shell commands with full filesystem access.

Code Runner

Execute Python and JavaScript with standard file I/O. Use native language APIs to read input and write output.

Computer

Persistent Linux environment with shell and file tools. For agents that need a dedicated machine.

WASM Plugins

Access workspace via WASI filesystem interface. Standard file APIs in any language — it just works.

Multi-Tool Workflows

How Tools Work Together

Real-world example of cross-capability file sharing

Input Arrives

User uploads a CSV file. It appears in /workspace/input/data.csv — accessible to all capabilities.

Python Processes

Code Runner reads /workspace/input/data.csv, processes it with pandas, and writes results to /workspace/output/processed.json.

Plugin Transforms

A WASM plugin reads /workspace/output/processed.json, applies business logic, and writes /workspace/output/transformed.json.

Sandbox Generates Report

Sandbox runs a shell script that reads the transformed data and generates /workspace/output/report.pdf using command-line tools.

Agent Delivers

Agent reads /workspace/output/report.pdf and returns it to the user. All steps shared the same storage.

Architecture

Technical Foundation

Built on cloud object storage with session isolation and quota enforcement

Session Isolation

Each session gets its own isolated namespace scoped to (account, channel, session). Complete separation between concurrent sessions.

Permission Enforcement

/workspace/input/ is read-only across all capabilities. /workspace/output/ supports full read-write. Validated at every access point.

Output Quotas

Configurable per-file size limits and file count limits on /workspace/output/. Enforced at write time to prevent runaway storage usage.

WASI Integration

WASM plugins access workspace via Wasmtime WASI filesystem interface. Pre-opened directories with standard POSIX-like file I/O.

Developer Experience

Familiar APIs. Zero Configuration.

Python in Code Runner

with open('/workspace/input/data.csv') as f:
  data = f.read()

# Process data...

with open('/workspace/output/result.json', 'w') as f:
  f.write(result)

Shell in Sandbox

# Same paths as Files capability
cat /workspace/input/config.json

# Process with any CLI tool
jq '.' /workspace/input/data.json \
  > /workspace/output/filtered.json

# Generate output
pandoc /workspace/input/doc.md \
  -o /workspace/output/report.pdf

Rust in WASM Plugin

use std::fs;

// WASI filesystem interface
let data = fs::read_to_string(
  "/workspace/input/data.json"
)?;

// Process...

fs::write(
  "/workspace/output/result.json",
  result
)?;

Standard file APIs in every language. No special SDKs. No configuration. Just works.

Platform Benefits

Why Unified Workspace Matters

True Multi-Tool Workflows

Chain different capability types seamlessly. Code Runner, Plugin, Sandbox — files flow naturally between tools.

No Integration Overhead

All capabilities share the same storage by default. No API calls to transfer data between steps. Just file paths.

Session Isolation

Each session operates in complete isolation. No cross-session access. Perfect for multi-tenant scenarios.

Language-Agnostic

Standard file APIs work in Python, JavaScript, Rust, Go, shell scripts. Use your language's native I/O — no platform-specific code.

Ready to Build Multi-Tool Workflows?

Unified Workspace is included in every tier. Start building seamless cross-capability pipelines.

Get Started Free Explore Capabilities