What is the purpose of associating a local folder with a project?
Understand optional directories and new task starting locations on the desktop client.
When is a directory needed
If you are working with an Agent on the desktop client around a local code repository or data directory, you can select a local folder when creating a project. This selection allows new Agent tasks to start from that directory, helping to keep the working location consistent. If you only want to organize chat tasks, you can skip the directory and create a regular lightweight project.
Selecting on the desktop client
When creating a project, the desktop interface offers “Local Folder (optional)” and “Use Existing Folder” options. After selection, check the displayed full path; if mistakenly selected, you can remove the chosen folder and reselect. If the desktop connection is not yet established, the page will indicate that the directory will be available for Agent use once the connection is ready.
- Open project creation on the desktop client.
- Select an existing folder and verify the directory and project name.
- After creation, confirm the connection status before starting a new Agent task.
Do not treat the directory as a permission boundary
The starting folder helps locate the work but does not mean the tool can only see this folder, nor is it a system-level isolation setting. When actual file operations are involved, specify the scope and content that must not be modified, and review the tool’s output. Associating a directory itself does not mean all files have been uploaded, nor does it mean old tasks have automatically switched to run in that directory. Before selecting, check whether the directory contains materials unrelated to the current work that do not need to be read.