Meet your shared workspace.
Corotation keeps ordinary project folders in sync through a server you control, called current. It is built for a small team working with code and large assets: the JavaScript, models, and textures that belong together.
Run cor work, keep using your editor and art tools, and let
related saves gather into sync packages. Current accepts the first valid
package in its entirety. Conflicting work stays local for you to repair.
Run one server and two clients on your own machine. Save a file, watch it arrive, and learn how to stop and resume.
Follow the tutorial →Pick your next step
Build from source and make the CLI available in your terminal.
Bring your teammateShare an address, keep credentials local, and connect a second machine.
Repair a conflictUnderstand a rejected package and choose the right result.
Recover a checkpointExport a baseline and protect your project against disk loss.
A few useful ideas
- Current is the authoritative server, not a folder you edit directly.
- A workspace is your local, editable project folder. Each person has their own.
- A package is a group of changes captured by a sync attempt. It is accepted or rejected as a whole.
- A chunk is a piece of file content addressed by its hash. Identical chunks are reused.
- A session names your continuous work and retains its exact accepted changes for later review. Start a session and add hooks.
- A baseline is an immutable checkpoint of the namespace, referring to existing chunks.
There is no commit command, branch workflow, or text merge engine. You can use Git separately for code if you want; Git is not required by Corotation.
Before using it for real work
Keep an independent backup. macOS has been tested; Linux and Windows behavior still needs validation. Historical chunks and local recovery copies currently accumulate because garbage collection is not implemented.
Read the current limits and the backup procedure before trusting a valuable project to a new setup.