Backup & sync with GitHub

Connecting a project to GitHub is optional — everything in Flywrite works offline. But with GitHub connected, your project is backed up off your computer and can sync across machines, all without typing a git command.

Connect a project to GitHub

Click the branch name in the top bar and choose Connect GitHub…, then follow the prompts. Once connected, the GitHub button opens your repo in the browser, and the top bar shows your sync state at a glance (like "synced" or "2 unsynced").

Sync

Press ⌘⇧S (a default — like every shortcut, it's customizable) or click Sync. One action checkpoints your work, pulls down anything new, and pushes your changes up. The Sync button sits in the top bar whenever a project is connected to GitHub, so you can bring things up to date any time you like. It spins while the sync runs — however you started it — and ignores a second click until it's done.

Flywrite watches the repo for you — when you open a project, when you switch back to the app, and every few minutes while you work. When there's something new waiting, the top bar tells you how far behind you are and a notification lets you know (turn that ping off in Settings → Notifications). That's all it does on its own: your files don't change until you click Sync, so nothing is ever rewritten under you mid-sentence.

Work on a second computer

On the other computer, add the project with Clone from GitHub and paste the repo URL (see Your first project). Write on either machine and hit Sync when you want them to match up.

The habit that makes this painless: Sync before you walk away from one Mac. When you sit down at the other one, Flywrite spots the new work on its own and shows you it's waiting — one click brings it down. If you've made changes on both machines, a single Sync sorts out both directions at once.

Sync your settings across Macs

Your app settings can sync the same way. Open your settings as a file (Settings → Edit settings file (JSON)) and connect the Settings project to a private GitHub repo, just like any project. On another Mac, open the Settings project and connect it to the same repo — Flywrite pulls your existing settings down and keeps both machines matched from then on.

Settings are the one thing Flywrite syncs for you. Every few minutes it sends your changes up and brings your other Macs' changes down in the background, so your theme, fonts and shortcuts follow you from desk to desk without you thinking about it. Two things it deliberately won't do: it holds off while you have settings open, so nothing shifts around mid-edit, and if you changed the same setting on two Macs it stops instead of guessing — you'll see a warning at the top of the Settings screen with a button to sort it out.

Prefer to do it by hand? Switch off Keep settings in sync across your Macs in Settings → General, and your settings will update only when you click Sync. Either way, anything you keep in local.json stays out of sync on purpose: that's the place for device-specific tweaks.

If both computers edited the same text

No scary conflict markers. Flywrite shows both versions side by side, in plain prose, and for each file you choose: Keep mine, Keep remote, Edit merged — or Resolve with Claude and let the agent sort it out. Then continue the sync, or abort it and stay with your local copy.