We shipped a quiet upgrade to how the Closo extension watches for marketplace login cookies. You won't see a new screen or button — this is plumbing — but it makes your sessions noticeably more durable. If you've been seeing yellow connection badges every few days, you should see fewer of them going forward.
What changed
Before this update: the extension would check your marketplace cookies every few minutes, in a polling loop. Most of the time, nothing had changed since the last check, so the work was wasted. When a marketplace did refresh a cookie (which happens during normal browsing), we'd miss it for up to a few minutes — sometimes long enough that the cookie expired before we picked it up.
After this update: the extension uses Chrome's webRequest API to listen for cookie changes the instant they happen. When Poshmark issues a fresh session cookie during your browsing, we capture it within milliseconds, not minutes. Same for Depop, Mercari, and Vinted — the four marketplaces that use browser-session cookies.
eBay and Shopify aren't part of this change. They connect over OAuth tokens rather than browser cookies, so there's nothing for the cookie listener to capture — those connections are kept fresh a different way and were already unaffected by the old polling behavior.
What you'll notice
Fewer 'session expired' yellow badges. The improvement compounds: when we catch every cookie refresh, our background scheduler has fresher data and refreshes need to fire less often. You'll see this most clearly on marketplaces you actively browse (your manual activity becomes free fuel for keeping Closo's session alive).
Listings that used to occasionally fail with 'auth required' should be more reliable, because we now have a fresher token at queue time.
What you won't notice
No new permissions — we already had webRequest. No UI changes. No new buttons or settings. This is a pure-plumbing improvement: better behavior, identical experience.
If you're curious about the technical architecture, this is part of what we internally call 'L1' — the layer of the extension responsible for identity capture. We documented it in an ADR (architectural decision record) on our internal engineering blog; we'll publish a summary externally later this year.
Check connection health