Bug with conflicting field edits between 1Password desktop and browser plugin

1P_Dave, The process I follow starts with the sign-up form on a web site. After filling the various forms (often with autofill help from 1Password), I accept the plugin's offer to save these fields. If the web site doesn't direct me to authentication settings, then I navigate there.

Next I open the desktop client so I can clean up the mess which the auto-save feature usually makes including manually moving things I want to keep out of the undesired "Saved on..." sections, then removing them and the unwanted saved fields in them. I often add fields such as email (which may not have been included), UID, handle, API keys, set tags and either reduce or replace the web site filed with a login page and sometimes adjust the autofill behaviour.
Note that even where possible to change details via the plugin, the fact that the interface disappears as soon as the pointers leaves it - precluding the ability to copy anything outside - makes doing so impractical.

It's usually around this stage when I'm setting up TOTP and passkeys that the plugin picks up the QR code and helpfully offers to save.
Accepting that offer saves that key, but effectively renders all the changes I've made in the desktop client unsavable, else is lost when I subsequently save my changes in the desktop client.