Black Friday sale: 30% off Flywrite
The short version

Create an empty private repository on GitHub, open your writing folder in Flywrite, choose Connect GitHub… and paste the repository's address. From then on, press Sync: one action saves a checkpoint, pulls new changes and pushes yours, with no git commands. It works through your Mac's Git, which needs to remember your GitHub login once.

We make Flywrite, the Markdown writing app these steps use.

What you'll need

  • A Mac: Flywrite is a Mac app.
  • Flywrite.
  • A free GitHub account. GitHub Free includes unlimited private repositories (GitHub's plans).
  • Your writing as Markdown files in one folder: a newsletter, a course, a book or notes (Your first project).
  • Your Mac's Git signed in to GitHub. Flywrite uses the Mac's own Git and has no GitHub login of its own. If this Mac has never pushed to GitHub, set up GitHub CLI (gh auth login) or Git Credential Manager once, as GitHub's guide shows.

Do it step by step

By the end, your project is in a private GitHub repository you own, one action (⌘⇧S) backs it up, and each checkpoint links to its commit on github.com. Flywrite stores none of it.

  1. Create an empty private repository on GitHub. On github.com, select + in the upper-right corner, then New repository, give it a name and choose Private. Leave the README, .gitignore and license options off, as GitHub advises when you bring in an existing project, then click Create repository and copy its HTTPS address.

    https://github.com/you/weekend-gardener.git

    You should see the new, empty repository on github.com. The address above is an example.

  2. Open your writing folder in Flywrite. Choose Open Folder and pick the folder your Markdown files are in, or New Project to start fresh. A project is just that folder; Flywrite adds no special format.

    weekend-gardener/
      ideas.md
      issues/
        2026-11-07-issue-42.md

    You should see your files in the file tree.

  3. Save a checkpoint. Press ⌘⇧C, or click Checkpoint in the top bar, so the files you have now go up when you connect: an empty repository receives your saved checkpoints as they are. Flywrite saves a checkpoint of the whole project when Claude Code starts in its terminal, and when Cursor Agent starts after its one-time setup. Codex and other CLI agents don't trigger it, so press ⌘⇧C before you start them.

    ⌘⇧C   Checkpoint Now

    You should see the new checkpoint at the top of the Versions panel (⌘⇧V).

  4. Connect the project. Click the branch name in the top bar and choose Connect GitHub…. Flywrite asks for one thing, the repository's address: paste it and press Enter.

    Connect a GitHub remote
    (create the repo on GitHub
    first — existing commits
    are pulled in)

    You should see "Remote connected and branch pushed", and the top bar shows the sync state. If it says "Could not reach the remote — check the URL and your access", check the address and sign your Mac's Git in to GitHub (What you'll need), then connect again from the command palette: ⌘⇧P, then Git: Connect GitHub Remote….

  5. Sync when you stop writing. Press ⌘⇧S, or click Sync (these are Flywrite's default shortcuts; every one is customizable): one action saves a checkpoint, pulls down anything new and pushes your changes up. Flywrite checks GitHub when you open the project, when you switch back to the app and every few minutes, and tells you when there's new work; your files change only when you Sync.

    ⌘⇧S   Sync Project

    You should see the sync state in the top bar, like "synced" or "2 unsynced".

  6. Check the copy on GitHub. Click GitHub in the top bar to open the repository in your browser. In Versions, checkpoint names are links: click one to open that commit on github.com.

    GitHub (top bar)
    ⌘⇧V, then click a
    checkpoint's name

    You should see your files on github.com, and your synced checkpoints as commits.

  7. Open it on a second Mac (optional). On the other Mac, add the project with Clone from GitHub and paste the same address; that Mac's Git needs your GitHub login too. Sync before you leave one Mac, and the other shows the new work waiting. If both Macs changed the same text, Flywrite shows both versions side by side and you choose (Backup & sync with GitHub). For the full routine and what to do when edits clash, see Sync a writing project between two Macs.

    Clone from GitHub
    https://github.com/you/weekend-gardener.git

    You should see the same files on the second Mac.

When not to use this

  • You want a copy of the whole Mac. Time Machine backs up your files, apps and documents to a USB drive or other external storage (Apple's guide).
  • You'd rather keep writing in the app you use now. GitHub Desktop commits and pushes any folder from a graphical app instead of the command line (Getting started with GitHub Desktop).
  • Your project holds large audio or video files. GitHub blocks files over 100 MiB, and Git warns over 50 MiB, so keep media outside the project folder (GitHub's file size limits).
  • You can't sign this Mac's Git in to GitHub. Checkpoints still keep versions you can restore on the Mac (Checkpoints & versions); for a copy off it, use Time Machine.
Back up your writing to your own GitHub

Flywrite is $99 a year for Mac, with no AI fee. Read about GitHub backup & sync.

Buy now

Questions

Is a checkpoint a backup?

Not on its own. A checkpoint is a Git commit that stays on your computer. For a copy off it, connect the project to GitHub and Sync.

Do I need to know Git?

No. Checkpoints and Sync are buttons and shortcuts in Flywrite, and nothing in this guide is a git command. Your Mac's Git only needs to remember your GitHub login once, which GitHub CLI or Git Credential Manager sets up.

Sources
  1. Flywrite docs: GitHub backup & sync. Checked .
  2. Flywrite docs: Checkpoints & versions. Checked .
  3. Flywrite docs: The terminal. Checked .
  4. Flywrite docs: Your first project. Checked .
  5. Flywrite docs: Keyboard shortcuts. Checked .
  6. Flywrite pricing. Checked .
  7. GitHub Docs: Creating a new repository. Checked .
  8. GitHub Docs: About remote repositories. Checked .
  9. GitHub Docs: Caching your GitHub credentials in Git. Checked .
  10. GitHub's plans. Checked .
  11. GitHub Docs: About large files on GitHub. Checked .
  12. GitHub Docs: Commits. Checked .
  13. GitHub Docs: Getting started with GitHub Desktop. Checked .
  14. Apple Support: Back up your Mac with Time Machine. Checked .

Write with your agent in a writing app.

Buy now