How browser-session seller tools work
Understand extension pairing, session health, active executors, standby devices, signatures, and safe failover.
The browser remains the session source
The seller signs into the marketplace directly in Chrome. The extension checks whether the expected marketplace tab and authenticated session indicators exist. The product can then report session health and execute approved browser actions without collecting the marketplace password.
A session is not permanent. The product must show when synchronization is stale or the marketplace has signed the user out.
Pair the device, not the password
A short-lived Pair Code links the extension to the correct workspace. The extension creates a local signing key and receives a revocable installation credential. Sensitive requests include a timestamp, nonce, body hash, and signature so old requests cannot be replayed easily.
Production builds should use a stable extension ID and minimum-version enforcement.
One active executor
Multiple devices may be registered, but one device should hold the execution lease. A fencing token lets the server reject late results from an old executor after failover. Commands also need expiration times so a disconnected device cannot execute a two-day-old action when it returns.
Standby devices are useful only when they have a valid synchronized session for the same seller account.