Official plugins

Reviewed OpenPets companion plugins, catalog lineup, bundling defaults, and companion-first behavior rules.

OpenPets plugins are reviewed companion features that run through the desktop plugin host. Users install and enable them from the Control Center. Maintainers ship them through the plugin catalog, and plugin authors can study them as SDK v3 examples.

This page is intentionally practical. It answers:

which plugins are in the current catalog
which official plugins are bundled with the app
which bundled plugins are enabled by default
how OpenPets plugins should behave
where to update code when the lineup changes

For the plugin architecture, permissions, runtime, sandbox, and packaging flow, see Plugin platform. For the author-facing API, see Plugin SDK v3.

Current catalog lineup

The public plugin catalog is web/public/plugins/catalog.v2.json. The current catalog contains ten official plugins and three community plugins.

Plugin	Type	What it does
Calendar Airmail	Official	Delivers Google Calendar event reminders through a selected bundled courier sprite.
Morning & Evening Routine	Official	Runs morning and evening check-ins.
Focus Buddy	Official	Starts focus sessions and reports timer progress through the pet.
Daily Fortune Cookie	Official	Shows scheduled or command-triggered fortune messages.
Launch Buddy	Official	Helps with launch/checklist moments.
Magic 8-Ball	Official	Answers command-driven yes/no style questions.
Mood Check-in	Official	Prompts lightweight mood logging and check-ins.
Quick Reminders	Official	Creates reminders with due/missed alerts, snooze, done, status, optional notifications, and sound.
Virtual Pet	Official	Adds Tamagotchi-style state, actions, and a pinned HUD.
Water Reminder	Official	Runs hydration reminders on a configurable cadence.
Higgsfield Watch	Community	Catalog-listed community plugin.
Spotify Buddy	Community	Catalog-listed community plugin.
Walkabout	Community	Lets the pet roam, follow the cursor, or patrol.

Official plugin source lives under plugins/official/. Community catalog plugins are labeled publisherType: "community" and are never bundled or enabled by default.

Bundled defaults

The desktop app can ship selected official plugins inside the application bundle. Those defaults are defined in apps/desktop/src/plugin-service.ts.

Default	Plugins
Bundled with the app	Quick Reminders, Focus Buddy, Launch Buddy, Virtual Pet
Enabled by default	Quick Reminders, Focus Buddy, Launch Buddy
Bundled but disabled by default	Virtual Pet

Everything else is installable from the catalog, not preloaded into a fresh app install.

The same file also defines staleBundledPluginIds, a cleanup list for old bundled plugins that should be removed during upgrade. Keep that list when old plugin ids need a clean migration, but do not optimize new runtime behavior for deprecated plugin names.

Companion behavior rules

OpenPets plugins should feel like companion behaviors, not mini control panels.

Host-rendered UI. Plugins describe bubbles, alerts, HUDs, commands, deliveries, sounds, schedules, and stored state. The desktop host validates and renders those effects.
No JSON editing for users. Settings come from typed configSchema fields rendered by the Control Center.
Localized by default. Manifests use $t: keys and code uses ctx.t(). Ship at least locales/en.json; add other locales when a plugin is part of the official lineup.
Small appliances beat giant knobs. A plugin should do one clear thing and explain itself by name.
Commands belong on the pet. Enabled plugins expose clear, verb-first commands through the default pet right-click menu. Bubble buttons and pinned HUDs handle in-the-moment actions such as snooze, done, feed, or dismiss.
State survives sleep and restart. Reminders, routines, focus sessions, and virtual-pet stats persist through ctx.storage and reconcile after resume.

Maintainer checklist

When plugin lineup, bundling, or catalog behavior changes:

Update plugins/official/*/openpets.plugin.json or the community plugin source.
Update apps/desktop/src/plugin-service.ts if bundled or default-enabled plugins changed.
Regenerate and commit the plugin catalog output under web/public/plugins/.
Update this page and Plugin platform when behavior, permissions, commands, or packaging rules changed.
Run the plugin release validators listed in Testing and validation.

Do not leave an older plugin lineup in docs after changing catalog output. The source of truth is the plugin source plus the generated catalog that the desktop actually consumes.