Ákos Kőműves I know that but here's the problem. localStorage is domain based. So when you switch to different tab for different website, your extension won't persist the session. There has to be an extension wide solution which is only (as far as i imagine) possible with chrome.storage.local Also, since you can't utilize localStorage, your background script can't use it for JS sdk. Service workers have their own runtime outside of window. If we want to have RLS active and use the database features, it's not possible extension-wide with the current session mechanism. I wonder how you would solve those problems? I ask because mainly those are the problems that I am trying to solve but there is no proper information anywhere in the internet :)

I don't understand how did you handle the session management here. You are using getSession() method from supabase js on your background script but it can't turn anything because supabase can't initialize session on your extension on the background script. I am using oauth client to login with my background script. I can login but I can't use any other method because supabase can't set session data to chrome.storage.local Even tho, I explicitly refreshSession on my background script, it returns the new session but doesn't add anywhere. So it disappears in the first browser refresh. How do you keep the extension session live inside your background script? I ask this because there is no info for cross-tab session management inside extensions anywhere in the internet :) Just because I don't have valid session stored anywhere in my background script, I can't use RLS with supabase-js. Also just because I can't use RLS I can't share my anon_key. Any ideas/opinions on this?