Saved items
Prompts, passages, commands, replies, and references you choose to keep. One permanent model, with behavior matched to the job.
Saved textQuick replacementTemplate
Writing memory for macOS
Remember what you meant, even from a fragment.
Koru is being designed to bring saved writing, reusable templates, and recent clipboard items to the caret, locally on your Mac.
Free and open source. No account planned for the core app.
Pre-release: no supported app download exists yet. Koru is in product definition and native feasibility work.
One recall surface
One place for what lasts, what repeats, and what was just copied.
Recent clipboard
Temporary material for now. Search or use it before it expires, then explicitly create a separate saved item when it is worth keeping.
Opt-inTemporaryLocally retained
The planned interaction
Recall without interrupting ordinary writing.
Remember a fragment
Search by the words you recall, not only an exact title or private abbreviation.
Begin with a fragment
At position zero in a fresh input, type a matching fragment. Empty focus alone never opens Koru; the global hotkey is the manual path.
Save before it disappears
Select useful writing and save it deliberately, with shortcut and macOS Service fallbacks where the host app permits.
Keep memory close
The core is designed for local encrypted storage, visible exclusions, pause, retention, export, and deletion controls.
Three deliberate steps
Invoke. Recall. Choose.
Invoke
Use a registered Koru shortcut where you are writing, or begin an eligible fresh-input fragment when typed matching is enabled.
Recall
Use a partial title, match term, body word, or the planned clp command for recent clipboard material.
Insert or keep
Explicitly insert or copy a result, save a selection, or turn a temporary clipboard entry into a separate permanent saved item.
Privacy as a contract
Your writing memory should be understandable.
The build plan makes the intended security model inspectable now. The released app must still prove every item through source review and testing.
- Clipboard history off until explicitly enabled.
- No raw keystroke persistence and secure fields ignored.
- No cloud sync, content analytics, or automatic support upload planned for the initial release.
- Encrypted content at rest with a non-synchronizing Keychain key.
- Visible pause, exclusions, retention, export, clear, and reset controls.
Compatibility
Tested support, not “works everywhere.”
Koru has no verified application matrix yet. The feasibility phase will test native fields, browsers, web editors, Electron apps, IDEs, and terminals across the supported macOS range.
Current state: under evaluation. Where caret bounds, selection access, or direct insertion are unavailable, Koru must fall back safely to a registered hotkey, stable panel placement, macOS Services, or copy-only behavior.
Apache-2.0
Built in the open.
Follow the roadmap, inspect privacy-sensitive decisions, report compatibility findings, or help build Koru.
builderking/koru
The repository includes the complete product, privacy, accessibility, release, and operations plan before implementation claims are made.
FAQ
What you should know before Koru ships.
What does Koru capture?
The planned app stores saved items only after an explicit save. Clipboard history will be off until you enable it. Typed matching will keep only the minimum current prefix in memory for an eligible fresh input and will never persist raw keystrokes. These behaviors are requirements, not claims about a released build.
Does Koru upload my writing?
The initial release is designed to make no background network requests and to keep saved and clipboard content local. There is no released app to verify yet, so the public source, network tests, and release evidence must confirm this before launch.
How is Koru different from text replacement and clipboard history?
Koru is designed around one recall surface for permanent saved writing and temporary recent clipboard material. It starts from the fragment you remember, while exact triggers remain optional accelerators.
Does it replace Raycast, Alfred, or my current text expander?
Not necessarily. Koru is intentionally narrower: capture, recall, and explicit insertion at the writing surface. Its actual compatibility and strengths will be measured during the native feasibility and beta stages.
Which Mac applications work?
No compatibility claim is published yet. The planned test matrix includes native apps, browsers, Electron apps, IDEs, terminals, and web editors. Unsupported contexts must use a safe hotkey, screen-relative, Services, or copy-only fallback.
Can I exclude password managers or specific apps?
The design requires secure fields to be ignored and includes user-visible Never Observe and Never Save Clipboard From lists. The exact bundled exclusions will ship in source and be verified before release.
Where is my data stored, and can I export or delete it?
The design uses encrypted local storage with a non-synchronizing Keychain key. Saved items will support explicit export and the app will provide clear-history, reset, and uninstall preparation. Exact paths and tested steps will be published with the first supported build.
Why will macOS request Accessibility or Input Monitoring?
Accessibility is needed for supported caret, selection, and insertion behavior. Input Monitoring is needed only if you enable typed matching. Registered global hotkeys are designed to remain available without Input Monitoring, with capability-specific fallbacks.
Is Koru free?
Yes. Koru is licensed under Apache-2.0. There is no paid tier or account requirement planned for the core app.
Follow the work
Stop rebuilding words you already got right.
Koru is not ready to install. Watch the public repository for feasibility results, beta instructions, and the first signed and notarized release.