Skip to main content
Open Files to browse the workspace’s WS Files area. This includes project folders, task inputs, working files, proofs, deliveries, and source material you are allowed to access. The Files explorer and the workspace panel serve different needs: Files is useful for broad folder management, while the panel opens a specific file beside chat.

Find and open files

Navigate folders with the tree and breadcrumbs, search or filter files, and use Go to path for an exact workspace path. Select a file to preview or open it in the appropriate panel. Use its path and ownership information to confirm that it belongs to the intended project or task. Common previews include text/source, Markdown, images, and supported document or spreadsheet formats. Preview support varies by file type; download a file when an in-app preview is unavailable.

Manage files

Where offered, replacement on a name conflict is an explicit option. Leave it off when you want the operation to fail rather than overwrite an existing item. Deleting a folder removes its contents. Review the selected paths and confirmation before proceeding. Removing a Task Detail attachment or a Drive sync folder is a separate action and does not itself delete that file.

Token files

Connect GitHub and GitLab offers a temporary file-upload method and a more secure Terminal method. A token uploaded to WS Files is an ordinary readable file, with no special secret protection. Follow the guide’s folder, handling, validation, and removal steps.

Edit supported content

A supported text or source file can open with Source or Edit controls in the workspace panel. Review the exact path, make the change, save it, and confirm the saved result. Closing a dirty file can prompt you to discard unsaved changes. This does not mean every binary document is editable in the preview. Use the format’s supported editor or download it where appropriate. Read-only roles can view and download allowed files but cannot change them.

Keep inputs, proof, and outputs organized

Use the task’s Task Files, Proofs, and Deliveries folders for its corresponding material. Use the project’s Working-files area for scratch work. If work has no tracked task, use an appropriate Working-files location rather than inventing a task association. A file existing somewhere in WS Files does not automatically make it an official task delivery. Attach or reference it through the task’s supported flow.