Skip to main content
Every collaborator on a repository gets their own workspace — a private space where you can make changes without affecting anyone else. Workspaces keep your uncommitted work separate and synced to the cloud automatically. If you’re not familiar with the concept, check out the Repositories, Branches, and Workspaces page first.

Cloned vs. non-cloned workspaces

A workspace can be either cloned (local) or non-cloned (cloud-only). Understanding the difference helps you decide how to set up your workflow.
Cloned (local)Non-cloned (cloud-only)
Where files liveOn your machine, synced with the cloudOnly on the Diversion cloud
How to edit filesUse any local editor, IDE, or game engineUpload files through the web or desktop app
Auto-syncChanges sync bidirectionally — local edits upload automatically, and remote changes download automaticallyNo local sync needed — everything is already in the cloud
Show in Explorer / FinderAvailable — opens the file’s location on diskNot available
Open with default appAvailable — opens the file with your OS’s associated applicationNot available
Disk usageUses local disk space for the full working copyNo local disk space used
When to use a cloned workspace: Most of the time. If you’re actively developing — writing code, editing assets in a game engine, or using any local tools — you need a cloned workspace so those tools can access the files on disk. When to use a non-cloned workspace: When you only need to browse files, review changes, or manage branches without editing locally. This is useful for lightweight access from a machine where you don’t want to download the full project, or for managing multiple workspaces without duplicating large repositories on disk. You can clone a non-cloned workspace at any time — see Cloning a workspace locally below.

Creating a new workspace

In the Desktop App:
1

Open the branch and workspace view

Click the branch dropdown in the left sidebar to open the branch and workspace view.The new workspace button in the branch and workspace view
2

Click 'New Workspace'

This opens the Create New Workspace dialog.The create new workspace dialog
3

Enter a workspace name

Give your workspace a descriptive name. This is required.In the desktop app, you can also check the Clone this workspace locally option to immediately create a local copy. If you choose to clone, you’ll need to pick a folder name and a directory on your machine.
4

Click 'Create' or 'Create & clone'

The workspace is created from the repository’s default branch. Once it’s ready, you’ll be navigated to the new workspace automatically.
For CLI usage, see clone command.

Renaming a workspace

1

Right-click the workspace

In the branch and workspace view, right-click on the workspace you want to rename and select Rename.Right-click menu with Rename option
2

Enter a new name

The Rename Workspace dialog shows the current name pre-filled. Type in the new name you’d like.The rename workspace dialog
3

Click 'Rename'

The button is disabled if the name is empty or unchanged, so make sure you’ve actually typed something different.
For CLI usage, see workspace command.

Deleting a workspace

1

Right-click the workspace

In the branch and workspace view, right-click on the workspace you want to delete and select Delete.Right-click menu with Delete option
2

Confirm deletion

The Delete Workspace dialog asks you to confirm. Keep in mind that all uncommitted changes in the workspace will be lost. If the workspace is cloned locally, you’ll see an additional warning that your local files will remain on disk but will no longer sync with Diversion. You’ll need to check a confirmation checkbox before proceeding.The delete workspace confirmation dialog
3

Click 'Delete'

This action is permanent — the workspace and any uncommitted changes are gone for good.
For CLI usage, see workspace command.

Cloning a workspace locally (Desktop only)

If you have a workspace that isn’t cloned to your machine yet, you can set up a local synced copy at any time.
1

Right-click the workspace

In the branch and workspace view, right-click on a workspace that isn’t locally cloned and select Clone.Right-click menu with Clone option
2

Pick a directory

A directory picker opens — choose where you want the local copy to live on your machine.
3

Wait for sync

Diversion creates a local copy and keeps it synced automatically. Any changes you make locally will be reflected in the cloud workspace, and vice versa.
For CLI usage, see clone command.

Attaching a workspace (Desktop only)

If you moved a repository to a different path on your machine, or if a workspace is not showing up after detaching a portable drive, you can re-attach it to Diversion.
1

Click the 'Attach Workspace' button

On the dashboard, click the Attach Workspace button in the top bar.Attach Workspace button on the dashboard
2

Browse to the workspace folder

A directory picker opens. Navigate to the folder containing your workspace (the folder with a .diversion directory inside it).
3

Click 'Connect'

Diversion will look up the workspace on the server and reconnect it. You’ll see a confirmation message once the workspace is successfully re-attached.
The workspace folder contains a hidden .diversion directory that Diversion uses to track workspace state. This folder must remain in place and should not be modified or deleted. To verify it exists, enable hidden files in your file explorer (on Windows: View > Show > Hidden items; on macOS: press Cmd+Shift+.). If it is missing, or if the workspace was deleted from the server or you don’t have permission to access it, you’ll see an error message.

Change the folder name without re-cloning

You can change the folder name without re-cloning by following these steps: This is the workspace we will use for the example: Diversion Dashboard
1

Turn off the agent:

Right-click the Diversion icon in your system tray and select Quit, or end the dv.exe task in the Task Manager.Option a:System Tray QuitOption b:Diversion End Task
2

Rename the folder:

Change the folder name directly in your file explorer.Rename Local Folder
3

Restart the agent:

Run the command dv in your command line and verify it starts successfully. Alternatively, open the desktop app and click “start agent” when prompted.Option a:DV Command PromptVerify:DV CLIOption b:Start Agent Noti
4

Reattach your workspace:

Since the folder was renamed, the workspace will not be displayed. Click Attach Workspace.Attach Workspace
5

Connect to the new path:

Navigate to the path with the new folder name and click Connect.Connect Workspace
You should now be able to see your workspace: Change Folder Finished