The Markdown Comments Safari Web Extension brings native, inline markdown collaboration to GitHub repositories and documentation previews directly inside Apple Safari on macOS — with zero commits, zero branches, and zero PR overhead.
Open the .dmg and drag Markdown Comments.app into your /Applications folder (the DMG also includes HOW TO OPEN.txt with these instructions).
Launch Markdown Comments from /Applications.
[!NOTE]
First Launch Gatekeeper Notice: Because this open-source tool is self-signed without Apple’s $99/year developer subscription, macOS may display “cannot be opened because the developer cannot be verified”.
To open:
Method A (Right-Click): Right-Click (Control-Click) the app in /Applications → select Open → click Open.
Method B (macOS Sequoia Settings): If blocked, open System Settings → Privacy & Security, scroll to Security, and click Open Anyway.
Method C (Terminal): Run:
Terminal window
xattr-cr"/Applications/Markdown Comments.app"
2. Enabling the Extension in Safari
Safari requires user permission before activating self-signed extensions:
Step 1: Allow Unsigned Extensions:
Open Safari → Settings → Advanced (or Features for web developers).
Check “Show Develop menu in menu bar”.
In the menu bar, open Develop and check “Allow Unsigned Extensions”. (Authenticate with your Mac password or Touch ID if prompted).
Step 2: Enable Markdown Comments:
Open Safari → Settings → Extensions.
Check the checkbox next to Markdown Comments.
Step 3: One-Click Direct Load (Instant Alternative):
In Safari’s menu bar: Develop → Add Temporary Extension… then select the extension folder (PlugIns/Markdown Comments Extension.appex/Contents/Resources or chrome-extension/dist/safari).
Step 4: Grant GitHub Permissions:
Navigate to any pull request or markdown file on https://github.com.
Click the Markdown Comments icon in the Safari toolbar / address bar and select “Always Allow on This Website” (or “Always Allow on Every Website”).
The Safari extension strictly adheres to the Zero Personal Access Token policy:
It never requests, prompts for, or persists GitHub Personal Access Tokens (PATs).
All authentication lifecycles use the standard OAuth Device Authorization Flow (RFC 8628) via the official registered GitHub App (Iv23li9t461keXDcVS0T).
All tokens are stored in private, sandboxed WebExtension storage (browser.storage.local).