Workshop Cloud and Workshop Desktop can sync project files directly, without a separate GitHub repository. This lets you start a project on the web, continue on desktop, and push changes back — or the other way around.Documentation Index
Fetch the complete documentation index at: https://docs.workshop.ai/llms.txt
Use this file to discover all available pages before exploring further.
Web ↔ Desktop Sync is separate from GitHub Integration. GitHub sync connects your project to your own repository for version control and collaboration. Web ↔ Desktop Sync moves files between Workshop’s two environments — no GitHub account required.
How It Works
Push and pull to move your project files between Workshop Cloud and Workshop Desktop:| Action | What happens |
|---|---|
| Push from Desktop | Sends your local project files to Workshop Cloud |
| Pull to Desktop | Downloads the latest files from Workshop Cloud into your local project |
| Push from Cloud | Sends your cloud project files to Workshop Desktop |
| Pull to Cloud | Downloads the latest files from Workshop Desktop into your cloud project |
Getting Started
Starting from Workshop Cloud
Create and build a project in Workshop Cloud
Build your project on the web as usual. Your files are stored in the cloud workspace.
Push to sync
Open the project settings and click Push in the Web ↔ Desktop Sync section. This sends your project files so Desktop can download them.
Download on Desktop
In Workshop Desktop, go to the Projects page. Cloud projects that haven’t been downloaded yet appear at the top. Click the download button to pull the project files to your machine.
Starting from Workshop Desktop
Open the project settings on Desktop
Navigate to your project and open the settings panel. The Web ↔ Desktop Sync section appears under Integrations.
Push to sync
Click the Push to web button (up arrow). This sends your local project files so Workshop Cloud can access them.
Using the Sync Controls
The Web ↔ Desktop Sync section appears in the project settings panel under Integrations. It shows:- The last push and pull timestamps
- Sync status (when refreshed)
- Three action buttons:
| Button | Action |
|---|---|
| Up arrow | Push your changes to the other environment |
| Down arrow | Pull changes from the other environment |
| Refresh | Check the current sync status |
Sync Status
After clicking Refresh, the status indicator shows:| Status | Meaning |
|---|---|
| In sync | Both sides have the same files |
| Local ahead | You have unpushed local changes |
| Remote ahead | The other side has changes you haven’t pulled |
| Diverged | Both sides have independent changes |
Handling Conflicts
If both Workshop Cloud and Desktop have made independent changes to the same project, a pull may result in a merge conflict. Workshop detects this and prompts you:- Force pull overwrites your local files with the other side’s version. Workshop asks for confirmation before proceeding.
Web ↔ Desktop Sync vs GitHub Integration
Both features sync project files, but they serve different purposes:| Web ↔ Desktop Sync | GitHub Integration | |
|---|---|---|
| Purpose | Move files between Workshop Cloud and Desktop | Version control with your own GitHub repo |
| GitHub account required | No | Yes |
| Collaboration | Between your own Cloud and Desktop environments | With anyone who has access to the repo |
| Use together | Yes — both can be active on the same project | Yes |