Tuna

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 Combo 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.

Some extensions also add App Enrichment, which makes a specific app result browsable or adds app-specific actions.

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

Safari’s Last Download is a live subject: Resolve stages the latest item in Downloads, or you can choose a compatible file action directly. Resolve is selected by default.

Connecting Accounts

For extensions that use browser sign-in, start the connection in Settings under Sources. The Connecting… state stays visible if you leave and return to the page. You can choose Cancel while Tuna is starting the connection or waiting for the browser callback. Waiting attempts time out after 10 minutes for direct connections or 15 minutes for connections brokered by Tuna’s server. Once the callback starts the credential exchange, Cancel is no longer available and the exchange runs to completion.

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.