Last updated: November 2026
Use this page to create Local or Cloud Workspaces in GitKraken Desktop so you can organize repositories, run multi-repository actions, review pull requests across a group of repos, and share workspace context with a team. Cloud Workspaces require connected integrations, while Local Workspaces stay on your machine until you convert them.
Requirements and limits
- Workspace types: Local Workspace or Cloud Workspace
- Cloud Workspace requirement: The relevant hosting service integration must be connected in Preferences > Integrations
- Local Workspace scope: Stored on your machine until you convert it
- Cloud Workspace scope: Accessible across machines and shareable with teams or users
- Multi-repository actions: Clone, Fetch, Pull, Open, Locate, and Remove are available from the Workspace toolbar
- Conversion path: Local Workspaces can be converted to Cloud Workspaces after connecting a supported integration
| Workspace type | Stored where | Shareable | Requires integration | Cross-device access |
|---|---|---|---|---|
| Local Workspace | On your machine | No | No | No |
| Cloud Workspace | In your GitKraken account and connected service context | Yes | Yes | Yes |
GitKraken On-Premise users: Cloud Workspaces are not available in Serverless or Self-Hosted Server deployments. Use Local Workspaces to organize repositories in those environments. Features that depend on Cloud Workspaces, including Workspace Insights and Launchpad Team View, are also not available.
Quick Start
To open the Workspaces view: Click the Repo Management folder icon in the tab bar, or press Ctrl + Alt + O (Windows/Linux) or Cmd + Option + O (Mac).
To create a Cloud Workspace:
- Click + New Workspace and select Cloud Workspace.
- Name the Workspace, select a hosting service, and choose repositories.
- Optionally share with teams or users and add an icon and description.
To create a Local Workspace: Click New Workspace, select Local Workspace, name it, and browse to select repositories or a directory.
To act across multiple repositories: Select the checkboxes next to repositories, then use the toolbar to Fetch, Pull, Clone, Open, or Remove them in bulk.
To view pull requests for all repos: Open a Cloud Workspace and click the Launchpad icon to see PRs across the entire Workspace.
To convert a Local Workspace to Cloud: Open the Workspace and click Create Cloud Workspace. You need a connected integration in Preferences > Integrations.
Workspaces are in the Repo Management tab.
How to access your Workspaces
To open the Repo Management tab, do one of the following:
- Click the Repo Management folder icon in the tab bar.
- Press Ctrl + Alt + O (Windows/Linux) or Cmd + Option + O (Mac).
How Cloud Workspaces work
Cloud Workspaces are available from any machine, and you can share them with selected teams in your organization. Use them to run multi-repository actions and manage pull requests for all their repositories in one place.
Note: Cloud Workspaces are not available in GitKraken On-Premise Serverless or Self-Hosted Server deployments. See How Local Workspaces work for the supported alternative in those environments.
Use a Cloud Workspace when: you need to share repository groups across machines or with teammates. Do not use a Cloud Workspace when: the repo list is only for your local machine and does not need shared or synced workspace context.
Watch the overview:
How to create a Cloud Workspace
- Click .
- Select Cloud Workspace.
- Name your Workspace and select the hosting service.
- Choose repositories to add.
- (Optional) Add an icon and description, and share the Workspace with teams or users.
Note:
Connect the hosting service’s integration in Preferences > Integrations first.
How to run multi-repository actions in a Cloud Workspace
To take action across multiple repositories:
- Select the checkboxes next to the desired repositories.
- Choose an action from the toolbar at the top.
Find more actions in the ellipsis menu.
These multi-repository actions are available:
| Action | Description |
|---|---|
Clone  |
Clone all selected repositories. GitKraken Desktop uses HTTPS unless SSH is configured in your settings. Only available if repositories are not already cloned. |
| Fetch | Fetch all selected repositories. |
Pull  |
Pull all selected repositories. Customize pull behavior from the dropdown menu. |
| Open in GitKraken Desktop or an external editor | Open all selected repositories in GitKraken Desktop or your default editor. |
| Locate in filesystem | Reveal local paths of selected repositories or update their location. |
| Remove | Remove selected repositories from the Workspace. |
How to view Workspace pull requests in Launchpad
See open pull requests for all repositories in a Workspace in Launchpad.
How Local Workspaces work
Use a Local Workspace when: you want a private repository grouping stored only on your machine. Convert to a Cloud Workspace when: you need cross-device access, sharing, or integration-backed workspace features.
How to create a Local Workspace
To create a Local Workspace:
- Click .
- Select Local Workspace.
- Name your Workspace.
- Browse to select one or more repositories. You can choose:
- Individual repositories
- A directory of repositories
- A VS Code Workspace file (
.code-workspace)
- (Optional) Add an icon and description.
To automatically add all repositories in a selected folder, enable the Sync with local directory option.
How to run multi-repository actions in a Local Workspace
You can take actions across multiple repositories within a Local Workspace:
- Select the checkboxes next to the repositories.
- Use the action toolbar at the top to:
- Fetch: Update all selected repositories.
- Pull: Sync selected repositories with the latest changes. Use the dropdown to customize pull behavior.
- Open: Open selected repositories in GitKraken Desktop or your default external editor.
- Remove: Remove selected repositories from the Workspace.
How to convert a Local Workspace to a Cloud Workspace
To share a Local Workspace or use it on other machines, convert it to a Cloud Workspace:
- Open your Local Workspace.
- Click Create Cloud Workspace.
- Choose a provider and select repositories to include.
- (Optional) Add more repositories from the same provider.
Note:
Connect the provider integration in Preferences > Integrations before you create a Cloud Workspace.
How to edit a Workspace
To edit a Workspace, click the ellipsis next to the Workspace name.
How to hide a Workspace
Hide a Workspace to reduce clutter. To show a hidden group again, such as Recents or Favorites, click the icon.
How to select or unselect repositories
Select repositories to run multi-repository actions, such as Fetch or Pull, on only those repositories.
How to open, clone, or locate repositories
Open repositories in GitKraken Desktop or your preferred editor. You can also clone or locate repositories within the file system.
How to edit Workspace details
Customize your Workspace’s name, color, description, and access permissions.
How to change Workspace color
Use color to visually organize and prioritize Workspaces. Select Change color from the ellipsis menu.
How to reorder Workspaces
Drag Workspaces to put them in the order you want.
How to use Insights to visualize pull request history
Note: GitKraken Insights is not available in GitKraken On-Premise Serverless or Self-Hosted Server deployments. Insights requires a connection to gitkraken.dev.
GitKraken Insights shows how pull requests are merged into your repositories. Insights supports GitHub.com, Bitbucket.org, GitLab.com, and Azure DevOps (Hosted), and gives you:
- A visual history of your repository’s development
- Pull request trends and team workflows
Insights runs on GitKraken.dev. To view it, open GitKraken.dev in your browser.
For more details, visit the GitKraken.dev Insights documentation.
Azure DevOps requirements for Workspace Insights
To use Workspaces and Insights with Azure DevOps, turn on third-party application access in Azure DevOps:
- In your Azure DevOps dashboard, go to Organization Settings > Policies.
- Enable Third-party application access via OAuth.
For details, see Microsoft’s guide: Change application connection & security policies for your organization.
