Plugins

Plugins

TypeWhisper for Linux uses the shared plugin model from the TypeWhisper codebase. Plugins add transcription engines, LLM providers, actions, post-processing, memory storage, and companion behavior to the app.

Plugin categories

This branch uses the following plugin categories:

Category	What it does	Examples
Transcription engines	Add local or cloud speech-to-text engines.	See [[Transcription engines
LLM providers	Add an LLM for prompt processing, cleanup, and memory.	See [[LLM providers
Action plugins	Run custom actions from transcriptions or prompt results.	Linear, Obsidian
Post-processing plugins	Transform text after transcription.	Script
Memory storage plugins	Persist and recall extracted memory entries.	FileMemory, OpenAiVectorMemory
Companion plugins	Observe app/plugin events and react.	Webhook

See Action, post-processing, memory & companion plugins for details on the action, post-processing, memory, and companion plugins.

Where plugins are loaded from

Plugins are loaded from the user plugin directory:

• ~/.local/share/TypeWhisper/Plugins/ on typical Linux setups

See Data and file paths for the full set of TypeWhisper data locations.

How bundled plugins are deployed

Bundled plugins live as source projects under plugins/ and reach the user plugin directory like this:

• Release builds run scripts/deploy-linux-plugins.sh to publish and bundle the Linux-capable plugins.
• The install script also bundles plugins into the published app.
• On first run, bundled plugins are copied into the user plugin directory if they are missing.

Per-plugin collection settings

Plugins that own user-editable collections — Webhook and Script — expose per-plugin collection settings under:

• PluginData/<plugin-id>/

Keeping the collections here means their entries survive plugin reinstalls, and the host can edit them through the settings UI without round-tripping a plugin process.

Known plugin gaps

• Marketplace/store browsing is intentionally not active in the Linux UI right now.
• Plugin update handling is limited compared with the intended full marketplace workflow.
• Some plugins may depend on external binaries, API keys, local model files, or services that must be configured separately.
• Plugins have been ported but are not all used day to day, so they are not guaranteed to all work 100%. If you find one with issues, open an issue or a pull request.

Related pages

• Transcription engines — the bundled local and cloud speech-to-text engines.
• LLM providers — the bundled LLM providers for prompts, cleanup, and memory.
• Action, post-processing, memory & companion plugins — Linear, Obsidian, Script, FileMemory, OpenAiVectorMemory, and Webhook.
• Plugin SDK — building your own plugins.
• Data and file paths — where plugins and plugin data are stored.

---

Changelog

Date	Change
2026-06-17	Initial version.
2026-06-17	Added Plugins page screenshot.