How Moket saves your work
Moket saves every change to your account in the cloud by itself. There is no Save button: close the tab or switch computers at any time.
Access: the top bar of the part editor shows where the part is and its save state.
| Top bar | Meaning |
|---|---|
My parts › Bracket | The part's project (click it to go there) and the part's name (click to rename) |
rev 12 | The part's revision: every saved change adds one |
rev 12 + 3 | Three changes are not on the server yet |
| Saving | Changes are on their way |
| Saved to cloud | Every change is in your account |
| Offline · 3 changes kept in this browser | The network is down. The changes wait in this browser and are sent when the network returns |
| Read-only | The part is being edited somewhere else, see below |
| Changed elsewhere | Your changes kept here and a newer revision need a choice, see below |
When changes are saved
A change is sent about a second and a half after you stop working, at least every 10 seconds while you keep working, and when you close or leave the tab. Each upload is one revision of the part, named after the changes in it, for example Edit Fillet1 and 2 more changes.
Before a change is sent, it is kept in this browser. If the tab closes or the network drops before the server has it, Moket sends it the next time you open the part in this browser.
One part, one editor
A part can be edited in one browser tab at a time. When you open it in another tab or on another computer, that one shows Being edited in Chrome on macOS (or another tab of the same browser) and the top bar shows Read-only. You can orbit, measure, use a section and export; editing is off.
- Click Edit here instead to move editing to this tab. The other tab shows Editing moved to ... and turns read-only; the changes it had not sent yet stay in that browser.
- When the other tab is closed, editing comes to this tab by itself within a minute.
- When another tab or an AI agent saves a newer revision while this tab is read-only, this tab shows it at once. If this tab still has changes it had not sent, Moket asks what to keep, as below.
When the part changed elsewhere
Changes kept in this browser can meet a newer revision of the part, for example when you worked offline while the part was edited on another computer, or when an AI agent saved changes while this tab still had some of its own. Assemblies, drawings and notes work the same way.
Moket then asks This part changed elsewhere (or This assembly changed elsewhere, and so on) and shows both sides: your changes and the newer revision. Until you choose, the document is read-only in this tab and AI agents cannot work on it. Both sides are kept whatever you choose:
| Choice | What happens |
|---|---|
| Keep my changes | Your changes are saved as a new revision on top of the newer one. The newer revision stays in Versions |
| Use rev 49 | The part continues from the newer revision. Your changes are saved as a separate part in the same project, named like Bracket (offline copy) |
Click Continue. Decide later keeps the part read-only with your changes in this browser; click Choose what to keep in the banner over the view when you are ready.
If you did not mean to change anything in this tab (moving a component with the mouse is a change too), choose Use rev ...: the tab shows the newest revision, with everything an agent or another computer added.
Undo
Undo and Redo work within the time the part is open in this tab. After a reload, the earlier steps are in the part's versions.