Speaker notes that screen-sharing tools can't see.
A pane floats above whatever you're demoing, showing one page of notes at a time. The window sets NSWindow.sharingType = .none, so Zoom, Teams, Meet, QuickTime and screencapture all skip it — the same mechanism password managers use to stay out of screenshots. You see your notes; the room sees your demo.
./build.sh
open build/SpeakEasy.app
Needs the Xcode command line tools (xcode-select --install). No other dependencies. To keep it around: cp -R build/SpeakEasy.app /Applications/.
| Default | Action |
|---|---|
⌃⌥→ |
Next page |
⌃⌥← |
Previous page |
⌃⌥H |
Hide / show the pane |
⌃⌥↓ ⌃⌥↑ |
Scroll inside a long page |
⌃⌥Space |
Start / stop auto-scroll |
Heads up on ⌃⌥Space: macOS uses it by default for "Select next source in Input menu." If it's taken, SpeakEasy tells you on launch rather than leaving a dead hotkey — free it in System Settings → Keyboard → Keyboard Shortcuts → Input Sources, or pick another combination in Settings.
Auto-scroll creeps the current page upward at a speed you set in the inspector (default 22 pt/s). It stops at the end of the page, when you change page, when you scroll by hand, and when you hide the pane. A ▶ next to the page dots shows it's running.
All reconfigurable in Settings (⌘,). They're registered through Carbon's RegisterEventHotKey, which means no Accessibility permission prompt — unlike the NSEvent global monitor approach, which needs you to grant input monitoring.
Shows the current page's heading and body, a row of dots for where you are in the deck, and a dimmed line along the bottom telling you what's coming next. That last one matters more than it sounds: knowing the next beat is most of what a presenter display is for.
Moving and resizing has no mode. While SpeakEasy is the frontmost app the pane is grabbable — drag it anywhere, drag the grip at its top-right corner to resize. Switch to any other app and it's click-through again, instantly. There's nothing to enable and nothing to get stuck in.
Three positions, in the inspector or the Pane menu.
Under camera is the default on a Mac with a notch. The pane rises to the top of the screen either side of the camera housing, with a bite cut out so the notch shows through — so you read your notes while looking down the lens instead of at the bottom of the screen. This is the good idea; I borrowed it from Oculta.
In this position the layout rearranges to use the strips beside the notch, which would otherwise be dead space: the page heading sits in the left flank and the progress dots in the right one. The body text then gets the full width below the housing, and gains back the vertical room a separate header row would have cost. If the pane is too narrow for the flanks to be useful, it falls back to the stacked layout automatically.
On a notched MacBook the menu bar is already split by the housing, so the space immediately either side of it is usually empty and the pane covers very little. On a display with no camera housing, Under camera tucks just below the menu bar instead — same eye-line idea, so plugging into a monitor mid-call doesn't move your notes somewhere surprising.
Bottom is a strip across the bottom, clear of app toolbars and browser tabs. Better for a screen-share demo, where the top of the screen has content in it.
Custom is set for you the moment you drag the pane, so hand-placing it never fights the automatic positioning. Pane → Reset Pane Position returns to the default for your display.
Nothing about the notch geometry is hardcoded per model: it comes from NSScreen.safeAreaInsets plus auxiliaryTopLeftArea / auxiliaryTopRightArea, so the cut-out lines up on any Mac that has a housing and is simply skipped on any that doesn't.
Long pages shrink to fit, down to a floor you set, then scroll. A small ▾ ▴ or ↕ next to the dots tells you there's more text; scroll resets to the top whenever you change page.
The default is See-through: a translucent fill in the tone macOS uses for dark panels, with a hairline edge, and no blur. Nothing behind the pane is softened, so you read your notes and watch your product in the same space. Drop the tint's alpha toward zero for barely-there, or raise it when readability matters more than seeing through.
Two other modes are available if you want them. Blur uses NSVisualEffectView with behind-window blending — frosted, which does obscure what's behind it. Liquid Glass (macOS 26+) uses NSGlassEffectView.
Worth recording why glass is the AppKit class and not SwiftUI's .glassEffect: the SwiftUI modifier samples only its own window's backing store, so on a transparent floating panel it has nothing to work with and degrades to a flat dark slab. The AppKit class samples the actual desktop. Two window properties are load-bearing for both glass and blur — backgroundColor = .clear and isOpaque = false. With an opaque window the material samples the window instead of the desktop.
Glass also looks milkier than the system volume/brightness HUD. Matching that exactly needs private Core Animation filters, which this app deliberately doesn't touch — they break on OS updates, and this is something you stand in front of clients with.
Because the pane is see-through, your text sits over content that isn't known in advance. So contrast is measured rather than eyeballed.
Next to the Text and Heading colours the inspector shows the measured WCAG 2.1 ratio with a ✓ or ⚠. The number is the worst case: the fill is composited over both a white and a black backdrop and the poorer of the two results is reported. If that passes, any backdrop passes. WCAG AA for body text is 4.5:1.
Fix Contrast nudges the text and heading colours toward whichever extreme helps until they clear 4.5:1. If adjusting the colours alone can't get there — which happens when the fill is very transparent — it also raises the fill's opacity, since that's the one lever that helps both colours at once.
The toolbar popup shows the current notes file and lists every markdown file in your notes folder, so switching decks is one click. It also holds New Deck, Rename, Duplicate, Reveal in Finder, Choose Folder, and Open Other File.
Import from PowerPoint takes the speaker notes out of a .pptx and makes a new deck: one page per slide, titled from the slide's title placeholder. Slides with no notes still become pages, so page numbers keep matching slide numbers — losing that alignment mid-demo is worse than a few sparse pages.
A .pptx is a zip of XML, so this shells out to /usr/bin/unzip and parses with Foundation's XMLDocument rather than taking on a zip dependency. It reads ppt/notesSlides/, not ppt/slides/, so on-slide bullets don't get pulled in, and it skips the slide-number placeholder PowerPoint puts on every notes page — otherwise every page would start with a stray digit.
Default folder is ~/Documents/SpeakEasy Notes/. Change it there or in Settings. If you used an earlier version that kept a single ~/Documents/speaker-notes.md, it gets moved into the folder on first launch.
Three panes, and it edits one page at a time:
- Left: your pages. Click to jump the pane to it, drag to reorder,
+/−to add and delete. - Middle: that page's title and body. Nothing else.
- Right: a collapsible inspector with a live preview of the pane against a stand-in desktop, presets, and appearance controls. Advanced options tuck behind a disclosure.
The selected page and the page on screen are always the same thing, so there's no hidden state to reason about.
Notes are stored as plain markdown in your notes folder, pages separated by ---, headings as # . That's a storage format — the interface never shows you a delimiter. You get a title field and a body field per page.
**bold** works, and lines starting with - become bullets. Edits autosave after about half a second. The file is also watched, so editing it in your own editor still works; unsaved changes in the app are never clobbered by the watcher. Pages → Open Notes File in External Editor if you'd rather work there.
Keep pages to one screen each. If a page needs scrolling, that's usually a signal to split it.
Check the invisibility once on your own setup. Start a screen share and look at the shared output on a second device, or use the meeting tool's own self-preview. You should see your screen with no pane on it. Quick local check:
screencapture -x /tmp/check.png && open /tmp/check.png
The pane should be absent from that file.
Two real limits. It only hides from software capture — a phone camera pointed at your screen sees everything, and so does anyone sitting next to you. And it lives on whichever display is NSScreen.main, repositioning when your display arrangement changes; if you present from a second monitor, check which screen it lands on.
Sources/Model.swift preferences, hotkeys, theme, the notes document
Sources/Pane.swift the click-through pane
Sources/Editor.swift main window: pages, editor, inspector
Sources/Settings.swift hotkeys, notes file, quick start
Sources/main.swift app delegate, menus, status item
Info.plist bundle metadata
build.sh swiftc -> build/SpeakEasy.app, plus icon generation
Resources/icon-art.jpeg source artwork
Tools/make-icons.py regenerates the icon PNGs from that artwork
build.sh turns Resources/icon-source.png into AppIcon.icns with sips and iconutil, both of which ship with macOS.
To change the artwork, replace Resources/icon-art.jpeg and run python3 Tools/make-icons.py (needs Pillow). It lifts the glyph off its background by luminance, so it wants dark line work on a light, roughly flat background.
The menu bar icon is a template image, so macOS recolors it for light and dark automatically. Detailed line art goes muddy at 18 points, so the script thickens the strokes before downscaling. If it still looks murky — particularly on a non-Retina display, where you only get the 18px version — delete Resources/MenuBarIcon.png and Resources/MenuBarIcon@2x.png and rebuild. The code falls back to the hand.point.up SF Symbol, which is drawn for that size.