My Sandbox
My Sandbox shows the status, resource usage, working directories, and terminal of your personal runtime environment, and provides entry points for the necessary sandbox operations.
Intended for: users who check their personal runtime environment.
Search keywords: My sandbox, Sandbox, sandbox, working directory, terminal.
What problems it solves
My Sandbox lets you view and use the personal runtime environment associated with your current account. You can run commands and scripts and save project files in an isolated environment, and you can also check resource usage, view available tools, and troubleshoot terminal or script execution issues.
To keep files and commands separate by project, you can create multiple working directories and select Skills, MCP, and a model for each directory.
On this page, Workspaces refers to the project directories in the sandbox, which the rest of this page calls working directories. They are different from the personal/shared workspaces in the navigation. To create a business space, manage space members and permissions, or configure space capabilities, see Create a space.
Enter the sandbox and check its status
Open the user menu and select My Sandbox. The page shows the sandbox information, CPU and memory usage, the working directory list, and the terminal area.
View status. The sandbox information area shows the name, running status, and last access time. Click the refresh button in this area to fetch the status again. Refresh in the working directory list rescans the directories.
Start and restart. When the sandbox isn't running and the page shows Start, click it and wait for the status to change to Running. While the sandbox is running or starting, the Restart option is available. You need to confirm again before restarting. Wait for the status to update during the operation, and don't click repeatedly.
Restarting interrupts the terminals and processes currently running in the sandbox. Reconnecting the terminal doesn't resume interrupted tasks. Check the task status first, and then decide whether to run them again.
View resources. CPU shows the cores used, the total cores, and the usage rate. Memory shows the used capacity, the total capacity, and the usage rate. The progress bars help you judge how high the current resource usage is.
When the resource area shows No sample yet, Resource metric unavailable, or Start the sandbox to view resource metrics, there are temporarily no metrics to display. This doesn't mean usage is zero. If CPU or memory usage stays high for a long time, first check for continuously running tasks, and then decide whether a restart is needed.
If no personal sandbox is bound or the sandbox is disabled, contact your administrator first. While the sandbox isn't running, you can't create, refresh, or open working directories.
Create and manage working directories
The working directory list shows each directory's name, path, and availability. Make sure your personal sandbox is Running before you work with directories.
- In the Workspaces area, click New and enter a name.
- In the creation window, select the Skills, MCP, and Workspace Model you need, and check whether the preselected options fit the current task.
- Click Create. The system generates a directory based on the name. After the directory is created, view it and its path in the list.
Refresh and rename. Click Refresh in the list to rescan the working directories in the sandbox. The Rename option next to a directory name changes only the display name. It doesn't rename the folder in the sandbox or change the actual path.
Open the terminal or browse files. Click a directory card to open or switch to that directory's terminal. Click the Files button on the card to expand or collapse the file panel. These are two different entry points.
In the file panel, you can enter subdirectories, return to parent directories through path navigation, preview text files, download files, upload files, and create folders. If a preview is truncated or a file can't be previewed, download the file to view it.
Deleting a file or directory requires confirmation. Deleting a directory also deletes its contents, which can't be recovered, so save any files you want to keep first. Don't casually delete unfamiliar directories, configuration files, or system-provided Skill content.
Configure directory capabilities
Click Configure on the target directory card, adjust the current directory's capabilities in Skills, MCP, and Workspace Model, and then click Save. If you only select options without saving, your changes aren't submitted.
Skills and MCP. Select the items you need from the capabilities available in the window. These settings apply only to the current working directory. They don't change the capability settings of personal/shared workspaces, and they don't apply the same settings to other directories.
Model. When you create a directory or select a model again, what's saved is the specific model that the directory always uses, and it doesn't change with the global default model. Some existing directories may show Global default model (Inherited). Once you change it to a specific model and save, the directory uses the selected model.
If the originally configured model is shown as unavailable, select an available model and save. If no models are available or the model list fails to load, follow the on-screen prompt first. If an administrator needs to configure or enable a model, see System Admin.
If saving fails, view the error details, fix the issue, and try again. If creation reports a failure but the directory already appears in the list, open that directory's Configure first to check and save any missing settings. Don't simply create it again.
Use the terminal and view tools
The terminal area lets you work with the sandbox command line directly in your browser. You can run common commands, run scripts, view files, or start development tasks in the terminal.
Select a working directory. Click a directory card first to open a terminal. Clicking the same directory again switches to its open tab. To open another independent terminal for the current directory, click + in the terminal area. You can't create a new terminal tab without selecting a directory.
Switch tabs and go full screen. You can switch among multiple terminal tabs. The bottom of the terminal shows the sandbox name and the number of open tabs. Click the full screen button to enlarge the work area, and click the exit button or press Esc to return.
Reconnect. When the terminal exits, the connection drops, or the service is unavailable, check the sandbox and model status as prompted on the page, and then click Reconnect. Don't assume that reconnecting restores the original process or task.
View tools. While the sandbox is running, click Tools to view the name, description, version, and commands of the available tools. This is a read-only list. It isn't used to install tools or change tool settings. If it fails to load, click Reload.
Operations such as restarting the sandbox, running scripts, and deleting files may affect current tasks. Make sure no important tasks are running before you proceed.
FAQ and next steps
| Problem | Suggested action |
|---|---|
| No personal sandbox bound, or sandbox disabled | Contact your administrator to bind or enable your personal sandbox. Creating a working directory doesn't solve this. |
| Directory still in the list, but a message says the folder was deleted | Refresh first to check the directory status. A list entry doesn't mean the folder still exists, and changing the display name doesn't restore files. To recover content, contact your administrator. |
| Directory status unknown or failed to fetch | Make sure the sandbox is running first, and then refresh the directory list. Until the check succeeds, don't conclude that the directory was deleted. |
| Terminal says the model is unavailable | Open the current directory's Configure, select an available model again, and save. If a message says the global default model is missing or unavailable, contact your administrator. |
| Status, tools, or file list fails to load | Use the refresh, reload, or retry option in that area. If it keeps failing, give your administrator the on-screen message and the time of the operation. |
Depending on what you want to do next, go directly to the relevant page:
- For an administrator to handle sandbox or model settings: System Admin.
- To create a personal/shared business space and set member permissions: Create a space.
- To return to your business conversations once your environment is ready: Conversations.
- To learn how to use the command line: CLI.
Parent section: Platform and Settings. You can continue reading from the related pages above.