Unlocking Desktop, doesn't unlock browser extention

I'm experiencing the same issue on Chromium, but it's as-if the extension is an entirely disconnected and separate app:

• Re-installing it and clicking it makes it want to 'sign in' to connect to my 1Password account.
• With the extension signed in and the desktop app unlocked, clicking the extension does not make it auto-unlock (even after waiting).
• With the extension signed in and the desktop app locked, clicking the extension does not make it auto-lock (even after waiting).

Honestly, the new extension gives me 1Password X-like PTSD symptoms, and almost makes me regret having a 20+ character password.

While I might be exaggerating a bit here, both of these apps (1Password X and the new beta extension) feel like they obstruct the goal I'm trying to accomplish instead of supporting me in leading a secure digital life, but I suppose that's feedback for a different team altogether.

EDIT: Could it be that the extension is failing to communicate in Chromium for a similar reason that the 1Password 7 extension failed in Chromium, because it was looking for / expecting a (hardcoded) path to Chrome's installation? I remember that with that version of the extension, 'creating' the path even if Chrome itself wasn't installed would magically make it work in Chromium as well.

EDIT 2: Found the 'path' workaround mentioned in my previous edit ( mkdir -p ~/Library/Application\ Support/Google/Chrome ), but even with that the problem still persists.