Assist is a platform where teams can build, host, and deploy internal AI software and agents in one place — giving companies a safe, controlled environment to standardize workflows and improve operations.

What are sandcastles?

Sandcastles are purpose-built internal apps created by non-technical teams on the Assist platform. They allow employees to build custom tools and workflows without engineering resources.

How much does Assist cost?

Assist uses pay-as-you-go pricing: provider costs + 5%, $0.17 per 1k tool calls, with no seat fees. Enterprise custom pricing is also available.

Do we need engineers to use Assist?

No. Assist is designed for non-technical teams to build and deploy AI tools. Engineers can use it too, but it doesn't require engineering resources to get started.

Disabling an Agent's Filesystem

This guide covers how to turn an agent's filesystem off, what happens to the files, and when to use this feature.

Before you begin

You must be the agent's owner, have edit or admin access to the agent, or be a workspace admin.
Understand that disabling does not delete any files. It hides them from the agent and removes the file tools from the agent's toolbox, but every file is retained and will come back if you turn the filesystem back on.
There is no undo prompt. The change takes effect immediately.

Steps

1. Open the agent edit page

From the main menu, go to Agents and click the agent you want to change.

2. Find the Filesystem Volume toggle

Scroll down to the bordered panel titled Filesystem Volume, just above Channel Mappings. The switch on the left shows the current state.

3. Turn the switch off

Click the switch. It flips to the off position immediately. A confirmation message appears at the bottom of the screen saying Filesystem volume disabled (files retained).

If the switch flips off and then slides back to on, the change failed. The most common causes are:

You do not have edit permission on the agent. Ask the owner or a workspace admin.
Your session has expired. Sign out and back in, then try again.

4. Verify in a new chat

Start a new chat with the agent and ask it to read one of the files it previously had. The agent will respond that it does not have access to a filesystem. This confirms that the file tools are no longer in its toolbox.

What happens to the files

Disabling is a soft switch. Nothing is deleted.

Every file the agent saved is retained exactly as it was.
The agent cannot read, write, edit, rename, copy, delete, search, download, or link to any of them while the filesystem is off. The tools are not available.
Files still count against the per-agent storage cap. Disabling does not free up the 100 MB allowance.
People with access to the agent can no longer see the files while the filesystem is off — the files are invisible until you re-enable.

When to disable

Common reasons to turn the filesystem off temporarily:

You want to stop the agent from reading old context. Disabling removes the agent's memory of what it previously saved so it starts fresh from the conversation. Turning the filesystem back on restores that memory.
You are auditing what the agent has stored. Disabling prevents new writes while you review, without destroying anything.
You are reconfiguring the agent's behavior. If you are iterating on the system message or tools and do not want file operations to confuse things, disabling keeps the files parked.

Re-enabling

Turning the filesystem back on restores every file exactly as it was before. See Enabling an Agent's Filesystem for the step-by-step guide.

The retained storage cap is unchanged on re-enable. If the agent was close to its 100 MB limit when you turned the filesystem off, it is still close to that limit when you turn it back on. See the storage-related entries in Troubleshooting if this becomes an issue.

Permanently deleting files

There is no one-click "erase everything" action in this release. To permanently free up storage:

Ask the agent, while the filesystem is on, to delete specific files or patterns. For example: "delete every file under /scratch/."
Ask your workspace administrator. Admins can clean up files through the workspace admin tools when needed.