Tensorlake Documentation

Use a versioned file system when many agents need the same files at a stable path. Put operating manuals, skills, configs, test fixtures, or binary tools in a file system. Update it from a laptop, CI job, or backend service. Agents mount it read-only. When an autosave checkpoint or permanent snapshot commits, following mounts refresh changed paths automatically.

Pattern

Store shared files in a versioned file system.
Publish updates from outside the sandbox with tl fs push.
Mount the file system into agents as a read-only directory.
Follow the file system for automatic distribution, or pin a permanent snapshot for fixed releases.

Create an Asset File System

CLI
Python
TypeScript

$ tl fs create agent-assets
Created filesystem agent-assets (empty).

from tensorlake.filesystem import FilesystemClient

client = FilesystemClient()
fs = client.create("agent-assets")

import { FilesystemClient } from "tensorlake";

const client = new FilesystemClient();
const fs = await client.create("agent-assets");

Keep the layout simple and stable:

agent-assets/
  manuals/
  skills/
  bin/
  configs/

Agents can refer to paths like /opt/agent-assets/manuals/operator.md, /opt/agent-assets/skills/research/SKILL.md, or /opt/agent-assets/bin/validator.

Publish From Outside a Sandbox

The producer does not need a sandbox, and it does not need a mount. Push a directory and create a permanent snapshot for the release:

$ tl fs push ./agent-assets agent-assets -m "publish agent assets"
Pushed ./agent-assets to agent-assets (48 file(s)).

Pushing the same directory again uploads only what changed — the right shape for a CI job or release service that republishes on every change. Pass -m on the changed push that should create a permanent snapshot; without it, the push creates an ephemeral autosave checkpoint. A push with no changes is a quiet no-op. Pushes honor .gitignore, preserve symlinks, and preserve executable bits on regular files. A file system has no special .git handling — only .gitignore governs what is excluded.

Mount Into Agents

Mount the file system read-only at a predictable path:

CLI
Python
TypeScript

$ tl fs mount agent-assets /opt/agent-assets --ro
Mounted agent-assets at /opt/agent-assets (read-only, follows the filesystem)

mount = client.mount("agent-assets", "/opt/agent-assets", readonly=True)

const mount = await client.mount("agent-assets", "/opt/agent-assets", true);

New sandboxes read the current state. Running following mounts refresh as the shared timeline advances, so updated manuals, skills, configs, and tools appear without rebuilding sandbox images. Agents should write outputs to a separate writable mount. Keep shared assets read-only so every agent sees the same source files.

Version Releases

Use a pinned permanent snapshot when a run must be reproducible:

tl fs mount agent-assets:9f2a1c8e4d6b1a0f3c7e9d2b8a4f6c1e0d3b7a99fedcba987654321001234567 /opt/agent-assets --ro

Pinned mounts stay fixed for the lifetime of the sandbox. Find permanent snapshot IDs under Snapshots in tl fs history agent-assets. Recent autosave IDs can expire and should not be used as long-lived release anchors. If you need named release channels (stable, canary) that you advance deliberately, back the assets with a Git repository and use branches as channels — that’s the surface built for explicit publication.

Binary Tools

Put tools under a stable directory such as bin/ with the executable bit set, and push:

chmod +x agent-assets/bin/validator
tl fs push ./agent-assets agent-assets -m "add validator tool"

Agents can call the tool directly:

/opt/agent-assets/bin/validator --input /work/result.json

Choose a Mount

Need	Use
Roll out the latest manuals, skills, or tools to many agents	Following read-only mount
Keep an eval, benchmark, or release run fixed	Pinned read-only mount
Publish assets from CI or an external service	`tl fs push`
Let an agent create or modify files	Writable mount

Overview

Guides

Reference

Use Cases

Distribute Files to Agents

Pattern

Create an Asset File System

Publish From Outside a Sandbox

Mount Into Agents

Version Releases

Binary Tools

Choose a Mount

Next Steps

Read-only Mounts

File System Mounts

​Pattern

​Create an Asset File System

​Publish From Outside a Sandbox

​Mount Into Agents

​Version Releases

​Binary Tools

​Choose a Mount

​Next Steps

Read-only Mounts

File System Mounts

Pattern

Create an Asset File System

Publish From Outside a Sandbox

Mount Into Agents

Version Releases

Binary Tools

Choose a Mount

Next Steps