Skip to main content
A file system mount exposes repository content as an ordinary directory in a sandbox. The mount path is ephemeral. For writable mounts, Tensorlake creates a workspace behind the path and snapshots persist file state into that workspace. Start with a private writable mount unless snapshots should publish immediately or the mount should be read-only.
Install the file-system extension once on macOS. Linux needs no setup.

Choose a Mode

Every mode uses the same command shape:

Writable Mounts

Writable mounts are for agent sessions that create or modify files. The agent writes files in the mount, snapshots persist progress to the workspace, and promotion publishes finished work to a branch.
See Writable Mounts.

Read-only Mounts

Read-only mounts are for inputs and shared assets. Pin to a commit for reproducibility, or follow a branch to roll out updates to many sandboxes.
See Read-only Mounts.

Workspace Operations

Use workspace operations to inspect dirty files, reattach the persisted workspace after a sandbox restart, clean up old workspaces, diff snapshots, and restore an earlier state.
See Manage Workspaces.

Plain Git Boundary

tl fs manages workspaces. Plain branches, pull-style collaboration, and CI are ordinary Git workflows. See Git Repositories. Workspace refs such as refs/workspaces/... are reserved on the server and cannot be updated with direct git push.

Writable Mounts

Mount, snapshot, and promote agent work.

Read-only Mounts

Use pinned and following mounts for fixed inputs and shared assets.

Distribute Files

Roll out manuals, skills, configs, and tools to agent fleets.

Generated Code

Store generated apps, docs, and assets with snapshots and activity history.

Manage Workspaces

Inspect, reattach, clean up, diff, and restore workspaces.

Core Concepts

Repositories, workspaces, mounts, snapshots, and promotion.