Black Friday sale: 30% off Flywrite
The short version

You don't need a code editor. Keep each issue as a Markdown file in one folder, open the folder in a Markdown writing app with a real terminal under the page, and run Claude Code there. Select a paragraph, ask for an edit, and it lands in the file you're reading. Flywrite sends Claude Code your selection and saves a checkpoint of the project when it starts.

We make Flywrite, the Markdown writing app these steps use. The same setup works for YouTube scripts and course lessons.

What you'll need

  • A Mac
  • Flywrite
  • Claude Code installed (Anthropic's setup guide), with a paid Claude plan or a Console account (Claude pricing)
  • Your issues as Markdown files, or one issue copied into a .md file

Do it step by step

By the end, your issues sit in one folder of ordinary files you can open anywhere, Claude Code edits the issue you're reading, and you have a checkpoint to go back to.

  1. Put your issues in one folder. Keep one Markdown file per issue, plus any notes you want Claude Code to see. Flywrite treats a folder as a project, with no database or special format. This example is a fictional newsletter, The Weekend Gardener:

    newsletter/
      2026-11-07-issue-42.md
      ideas.md
  2. Open the folder in Flywrite. On the Welcome screen, or from + in the projects rail, choose Open Folder and pick the folder. Starting from nothing? Choose New Project instead. You should see the folder's files in the file tree; click 2026-11-07-issue-42.md to open it in the editor.

  3. Add a voice file (optional). Create a file called CLAUDE.md in the folder with your newsletter's rules. Claude Code reads it at the start of every session and treats it as guidance, not a rule it must follow, so keep it short and specific. A five-line example:

    This is The Weekend Gardener, a weekly newsletter for beginner home gardeners.
    Each issue is about 400 words, with one main tip and one seasonal reminder.
    Keep the tone warm and plain: short sentences, no unexplained jargon.
    End every issue with "See you in the garden."
    Never change quoted text or reader questions.
  4. Start Claude Code. Press ⌃2, or click + in the terminal tab bar and choose Claude Code. 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. These shortcuts are defaults, and you can change any of them. You should see a terminal tab named Claude Code under your draft.

  5. Select a paragraph and ask. Click into the issue, select the paragraph you want changed, then type your request in the Claude Code tab. Claude Code already sees your selection and the open file, so there's nothing to paste:

    Tighten the selected paragraph to under 60 words. Keep the tone.
  6. Choose whether Claude Code asks first, then read the edit in place. A terminal session of Claude Code usually starts in auto mode, which edits without asking you each time. To approve edits yourself, press Shift+Tab once before you ask: that switches to manual mode, which asks before Claude Code edits a file. You should see ⏸ manual mode on in Claude Code's status bar. As Claude Code edits, the issue updates in the editor. Read it in Rendered view, or press ⌘E for Source view.

  7. Keep it, or roll it back. If you like the edit, keep writing. If not, run /rewind in Claude Code, pick your request, and choose Restore code. Or open Versions with ⌘⇧V, expand the checkpoint from when Claude Code started, and Restore just the issue file. More in Roll back what an AI agent changed.

    /rewind
  8. Back up the folder (optional). To keep a copy off your Mac, back it up to your own GitHub repository: click the branch name in the top bar and choose Connect GitHub…. After that, one Sync action (⌘⇧S) checkpoints, pulls and pushes, with no git commands. You should see your sync state, such as "synced", in the top bar. See Backup & sync with GitHub.

When not to use this

  • You'd rather not see a terminal at all. Anthropic's Claude desktop app runs Claude Code in its Code tab, with a project folder for each session (Claude Code desktop docs).
  • Your newsletter lives only in your email platform's editor. Claude Code works on files, so copy an issue into a .md file first, or keep drafting where you are.
  • You don't write on a Mac. Flywrite is Mac only. Claude Code itself also runs on Windows and Linux (system requirements).
  • You only need the agent, not a writing view. Run claude in macOS Terminal inside the folder. /rewind still works there (checkpointing), with no automatic project checkpoint.
Write your newsletter with Claude Code in a Markdown writing app

Flywrite is $99 a year for Mac, with no AI fee. Read the Claude Code docs.

Buy now
Sources
  1. Flywrite pricing. Checked .
  2. Flywrite docs: Writing with Claude Code. Checked .
  3. Flywrite docs: The terminal. Checked .
  4. Flywrite docs: Your first project. Checked .
  5. Flywrite docs: The editor. Checked .
  6. Flywrite docs: Checkpoints & versions. Checked .
  7. Flywrite docs: GitHub backup & sync. Checked .
  8. Flywrite docs: Keyboard shortcuts. Checked .
  9. Claude Code: Set up. Checked .
  10. Claude Code: How Claude remembers your project. Checked .
  11. Claude Code: Choose a permission mode. Checked .
  12. Claude Code: Checkpointing. Checked .
  13. Claude Code: Desktop application. Checked .
  14. Claude pricing. Checked .

Write with your agent in a writing app.

Buy now