Extensions
Extensions let Tuna understand more domains.
They add new catalogs, actions, and app-specific objects, but they still plug into Tuna's normal command shape.
So an extension is not a separate island. It is more vocabulary for the same language.
What Extensions Add
An extension might add:
- new things to browse
- new search roots
- new actions for specific apps or object types
- connection-backed data from another service
That means an extension can show up naturally in Fuzzy Mode, participate in Leader Mode, or become a target for text and file commands.
First-Party Examples
Tuna already ships with extensions for parts of macOS and common tools, including things like:
- Notes
- Reminders
- Safari
- Obsidian
- Things
- GitHub
Some of these depend on apps, permissions, or connection settings, so what you see may differ from one Mac to another.
How To Think About Them
Do not think "now I am using an extension."
Think "Tuna now has more subjects and actions available."
That mental model keeps extensions simple:
- a Note can become a subject
- a GitHub pull request can become a subject
- a Safari current page can become a subject
- their actions work the same way other Tuna actions work
When Something Is Missing
If an extension is installed but not useful yet, usually one of three things is true:
- the catalog is disabled in Settings
- the source app or permission is unavailable
- the extension needs connection setup
Public Docs Scope
The public docs focus on using extensions inside Tuna.
If you just want the bigger picture, it is enough to know that extensions are how Tuna grows without abandoning the core command model.