Persistence (Advanced)
- Build your first harness
- Host options
- Send and show media
- Connect clients
- Write a client in any language
- Access and tenants
- Run in the terminal
- Deploy a harness
- Send inputs safely
- Run a tool without a model
- Durable sessions
- Run background work on workers
- List, rename, and fork sessions
- Lifecycle and retention
- Run side effects once
- Wait for a person
- Build on the session log
- Control how a turn ends
- Store settings per thread
- Compact a long session
- Fork and reset a thread
- One log for a session tree
- Write a plugin
- Track usage and cost
- Ask before risky tool calls
- Give your agent coding tools
- Sandbox and extend the coding tools
- Run the coding tools for many threads
- Undo a turn
- Build a coding agent
- Delegate to coding agents
- Switch between agent profiles
- Auth and connectors
- Share a thread between people
- Connect model providers
- Build your own UI
- Code mode in a harness
- Work until a goal is met
- Run agents from a harness
- Hand off a conversation
- Add skills
- Use MCP servers
- Give your agent a computer
- Use from any MCP client
- Use a harness from an editor (ACP)
- Overview
- Quick Start
- Providers
- Harnesses
- Harness Auth
- Workspace
- Tools
- Policy
- Lifecycle & Snapshots
- Portable Snapshots
- Keep Files After Reload
- Save a Named Version
- Branch From a Version
- Send a Frozen File
- Let the Agent Save and Fork
- Pick Which Files to Keep
- What a Snapshot Stores
- Instance Durability
- Durable Runs
- Events
Sandboxes (Advanced)
- Runtime Context
- Bring Your Own Key
- Keep Keys on the Server
- Debug Logging
- Multimodal Content
- Files API
- Per-Model Type Safety
- Runtime Adapter Switching
- Tree-Shaking
- Extend Adapter
- Extend Adapter: Advanced
- Typed Pre-Configured Options
- Test with a Fake Model
- Prompt Caching
- Mid-Conversation Changes
- Approval Flow Processing
Pick Which Files to Keep
Limit which workspace files a portable snapshot stores. The agent can still write the rest of the workspace.
Pass a policy when you create the snapshots object. include and exclude are functions. They decide which workspace paths the capture stores. The same policy runs on automatic save, named save, and restore.
This page assumes you already created a snapshots object. If you have not, start with Keep Files After Reload.
Pass the policy#
Pass policy to memorySandboxSnapshots or createSandboxSnapshots. Then pass that same snapshots object to withSandbox. This sample keeps only the src folder:
import { chat } from '@tanstack/ai'
import { GROK_CLI_INSTALL_COMMAND, grokBuildText } from '@tanstack/ai-grok-build'
import { withPersistence } from '@tanstack/ai-persistence'
import {
createSecrets,
defaultSandboxSnapshotPolicy,
defineSandbox,
defineWorkspace,
InMemorySandboxInstanceStore,
memorySandboxSnapshots,
withSandbox,
} from '@tanstack/ai-sandbox'
import { dockerSandbox } from '@tanstack/ai-sandbox-docker'
const instances = new InMemorySandboxInstanceStore()
const sandbox = defineSandbox({
id: 'app-builder',
provider: dockerSandbox({ image: 'node:22' }),
workspace: defineWorkspace({
source: { type: 'none' },
setup: [GROK_CLI_INSTALL_COMMAND],
secrets: createSecrets({ XAI_API_KEY: process.env.XAI_API_KEY ?? '' }),
}),
lifecycle: { reuse: 'thread' },
})
const defaults = defaultSandboxSnapshotPolicy()
const snapshots = await memorySandboxSnapshots({
sandbox,
instances,
policy: {
...defaults,
include(path: string) {
return path === 'src' || path.startsWith('src/')
},
},
})
const result = chat({
threadId: 'app-thread',
adapter: grokBuildText('composer-2.5'),
messages: [{ role: 'user', content: 'Create a landing page.' }],
middleware: [
withPersistence(snapshots.persistence),
withSandbox(sandbox, { instances, snapshots }),
],
})
void resultsnapshots.save has no file list. Change the file set by changing policy on the snapshots object.
Default exclusions stay unless you pass exclude#
If you pass only include or only redact, the default exclusions stay in place. Capture still skips .env, .git, and node_modules.
If you pass exclude, that function replaces the default exclusions. Copy defaultSandboxSnapshotPolicy() first. Then keep those rules and add yours. Every recipe below starts with ...defaults for this reason. See Skip one extra folder.
The projection marker for this workspace stays protected. A custom policy cannot capture or restore that marker.
How include and exclude run#
Each path is a workspace-relative string such as src/app.ts. kind is file or dir.
- The projection marker is skipped.
- If exclude(path, kind) returns true, the path is skipped. For a directory, the whole tree under it is skipped.
- For a file, include(path, 'file') must return true. If you omit include, every file that is not excluded is stored.
- Capture then walks parent directories so a nested file can still match.
exclude wins. include: () => true cannot keep a path that exclude rejects.
Capture does not read a file that the policy skips.
Keep one file#
Return true only for that path. Capture still walks parent directories.
import { defaultSandboxSnapshotPolicy } from '@tanstack/ai-sandbox'
const defaults = defaultSandboxSnapshotPolicy()
const policy = {
...defaults,
include(path: string) {
return path === 'src/app.ts'
},
}Keep a few files#
import { defaultSandboxSnapshotPolicy } from '@tanstack/ai-sandbox'
const defaults = defaultSandboxSnapshotPolicy()
const keep = new Set(['package.json', 'src/app.ts', 'src/index.ts'])
const policy = {
...defaults,
include(path: string) {
return keep.has(path)
},
}Keep one folder#
import { defaultSandboxSnapshotPolicy } from '@tanstack/ai-sandbox'
const defaults = defaultSandboxSnapshotPolicy()
const policy = {
...defaults,
include(path: string) {
return path === 'src' || path.startsWith('src/')
},
}Keep files by suffix#
Allow directories so the walk can reach nested files. Then match the suffix.
import { defaultSandboxSnapshotPolicy } from '@tanstack/ai-sandbox'
const defaults = defaultSandboxSnapshotPolicy()
const policy = {
...defaults,
include(path: string, kind: 'file' | 'dir') {
return kind === 'dir' || path.endsWith('.ts')
},
}Skip one extra folder#
Keep the default exclude. Then add your folder.
import { defaultSandboxSnapshotPolicy } from '@tanstack/ai-sandbox'
const defaults = defaultSandboxSnapshotPolicy()
const policy = {
...defaults,
exclude(path: string, kind: 'file' | 'dir') {
if (defaults.exclude?.(path, kind)) return true
return path === 'dist' || path.startsWith('dist/')
},
}To skip a folder name at every depth, match a path segment:
import { defaultSandboxSnapshotPolicy } from '@tanstack/ai-sandbox'
const defaults = defaultSandboxSnapshotPolicy()
const policy = {
...defaults,
exclude(path: string, kind: 'file' | 'dir') {
if (defaults.exclude?.(path, kind)) return true
return path.split('/').includes('dist')
},
}What the policy does not filter#
The file policy applies to workspace files and empty directories only.
- The checkpoint still stores the full conversation for the thread.
- The checkpoint still copies every generated artifact for the thread.
See What a Snapshot Stores for secrets, default exclusions, and restore safety.
Restore#
Restore uses the same policy. Files that the policy does not include stay on the destination disk. Restore does not delete those files.
Automatic restore still writes the latest checkpoint into a new private sandbox. It does not write into a live resumed sandbox.