Supabase plugin requires re-authentication on every new session (regression)

Description

The Supabase MCP plugin now requires re-authentication every time a new session is started. Previously, authentication persisted between sessions.

Behavior

Expected: Supabase OAuth tokens persist between sessions. Opening a new session should automatically connect without requiring re-authentication.

Actual: Every new session shows "needs authentication" for the Supabase plugin, requiring the user to go through the browser OAuth flow again.

Timeline

• This started occurring around January 23-24, 2026
• The plugin was updated on January 23rd, 2026
• Prior to this update, authentication persisted correctly

Environment

• macOS
• Built-in plugin: plugin:supabase:supabase

Steps to Reproduce

1. Start a session
2. Authenticate Supabase via browser OAuth
3. Supabase connects successfully
4. Close the session completely
5. Start a new session
6. Supabase shows "needs authentication" again

Additional Context

OAuth refresh tokens do not appear to be persisted between sessions. No Supabase-related entries are found in macOS Keychain after authentication.