Spotify Plugin

Status: legacy / unsupported on current Sero builds. Sero now ships stock Electron and no longer includes the Castlabs Electron fork, Widevine CDM, or VMP signing required by the Web Playback SDK path.

Overview

Legacy Spotify app documentation for OAuth/PKCE and playlist browsing. DRM-dependent playback and Mini Player features are not expected to work on current stock-Electron Sero builds.

Try it first

  1. Install or activate the plugin from a trusted source. For local development, use Admin → Plugins → Local Plugin Development rather than treating an attached folder as an installed plugin.
  2. Open the app from the sidebar/App Store if the manifest exposes a UI.
  3. Use fake/demo data for the first run.
  4. Ask Sero for a small, reversible action before relying on the plugin in real work.

Activate the plugin, complete Spotify OAuth with a test/personal account you are comfortable using, then open the Spotify app.

Surfaces from the manifest/source

Surface Source-checked detail
Package @sero-ai/plugin-spotify
Status external/local
App state Manifest declares plugin-owned state under .sero/apps/<app-id>/... when an app is present.

Privacy, secrets, and recovery

Spotify auth and playback data are account data. Do not file playback bugs against current Sero builds unless you are intentionally maintaining a legacy Castlabs/Widevine fork.

If setup fails, confirm the plugin is active in the current profile, check required host capabilities, restart Sero, and collect redacted logs only. Do not include tokens, account identifiers, email content, banking data, health data, or private workspace paths in support reports.