Hodor

Instantly launch your saved prompts into any AI tool. Hodor is designed for AI-heavy users.

701 KB native macOS app · Free and open source

All local, no network, no data collection · Apple notarized

hodor.design — download and demo

ClipA_M.mp4

• Three Ways to Use It
• Design Choices
• Install
• Settings
• FAQ
• Why I Built This

Three Ways to Use It

• Screen edge — Slide to the screen edge. Browse your prompts, click to paste. (Or press Ctrl+Opt+Space to open from the keyboard.)
• Shortcut — Assign a letter A-Z to any prompt. Press Ctrl+Opt+R and it's pasted instantly.
• Keyword — Set a keyword like ;kit. Type it anywhere and your prompt replaces it in place.

All three get your prompt into the active text field — or onto your clipboard if nothing is focused. The sidebar is for browsing. Shortcuts and keywords keep your hands on the keyboard.

Design Choices

• Everything stays on your machine. Your prompts never leave your Mac. Zero network requests in the entire codebase — no analytics, no telemetry, no update checks. You can verify: search the source for URLSession — it's not there.

• No interruptions. No notifications, no "rate this app" prompts, minimal onboarding, no update nags. You open it, you use it, it gets out of your way.

• Quiet macOS visuals. Hodor follows Apple’s visual language, including Liquid Glass where available, so it feels like a quiet system utility: present when needed, nearly invisible when not.

• Native macOS, not Electron. Built with SwiftUI and SwiftData. No web views, no bundled browser.

• Accessibility permission — and nothing more. Hodor uses macOS Accessibility APIs to paste into other apps — the same approach as Raycast and Alfred. The source code is right here. You can see exactly what it does and what it doesn't.

• Free and open source. A small local tool with no infrastructure costs can be free, so I want to keep it free and accessible to more people. Every line of code is public.

• Why GPL v3? Hodor may handle sensitive prompts, so forks and improvements should remain open, inspectable, and accountable.

Install

Download the latest DMG from hodor.design or the GitHub Releases page.

Settings

Hodor keeps settings intentionally small:

• Sidebar position — place the sidebar on the left or right edge.
• Screen edge trigger — turn edge activation on or off.
• Display — use Hodor with dual displays: follow the focused screen or pin it to a specific display.
• Appearance — use system, light, or dark mode.

FAQ

• Why does Hodor need Accessibility permission?
  To paste prompts into other apps, Hodor simulates Cmd+V through macOS Accessibility APIs. The same permission lets it detect per-prompt shortcuts (Ctrl+Opt + letter) and keyword typing. That's all it's used for — Hodor doesn't record keystrokes, read screen content, or access other apps' data.

• I clicked a prompt but nothing was pasted.
  Your prompt is on the clipboard. Press Cmd+V to paste manually. This usually happens when no text field is focused in the target app.

• What's the difference between the sidebar and shortcuts?
  The sidebar is for browsing — find and click, no memorization needed. Shortcuts (Ctrl+Opt + letter) and keywords (;kit) are for when you're already typing — your prompt appears without leaving the text field.

• How should I set up keywords?
  Start keywords with a symbol: ;kit, /reply, .git. This prevents Hodor from triggering when you type normal words. Hodor ships with four seed prompts that show this pattern. One caveat: keywords that are prefixes of each other can't coexist (;ki and ;kit would conflict).

• Ctrl+Opt+Space conflicts with my input method switching.
  This is a known conflict. If you switch between input languages, macOS may already use this shortcut. Try changing your input method shortcut to Ctrl+Space or Caps Lock in System Settings > Keyboard. Custom hotkeys are planned for a future version.

• Where is my data stored?
  All prompts are stored locally on your Mac using SwiftData, in ~/Library/Application Support/Hodor/Hodor.store. Nothing is synced, uploaded, or sent anywhere.

Why I Built This

I work with AI tools every day and kept a growing collection of prompts — scattered across Raycast snippets, Notion & Apple Notes, and a doc that kept getting longer. Raycast snippets are useful, but long prompts are hard to browse and edit on the fly. The test I set: could I actually stop using Raycast's snippet system for this? I use it every day now.

Feedback

• Bug reports — open an issue
• Feature requests — start a discussion — upvote ideas you want to see
• Questions — ask in discussions

License

GPL v3 — Designed by Woody, AC & OC in NYC