Reporting three issues observed with the extension (v4.24.9, Chrome). Grouped into one report; happy to split if you prefer.
1. Cookies are not detected automatically
Symptom: After logging into a provider site (e.g. ChatGPT), the popup does not show the session as captured until some network activity happens on the page.
Likely cause: Cookie capture appears to rely solely on the chrome.webRequest.onBeforeSendHeaders listener firing on an xmlhttprequest (see background.js:65-89). If the user just lands on a provider page while already logged in and doesn't trigger an XHR carrying the session cookie, no capture entry (cap_<provider>) is ever created, so popup.js (~L901-902) shows nothing captured even though the user is authenticated.
Suggestion: Add an on-demand/periodic read via chrome.cookies.get/getAll (or the cookieStore API) when a provider tab is active, so a logged-in session is detected without waiting for an XHR.
2. Popup is very small / clipped
Symptom: The popup renders very small on open, with the footer clipped.
Likely cause: popup.css sized the popup with height: min(560px, 100vh); 100vh under-resolves during Chrome's initial popup layout, so min() picks the tiny value, and overflow:hidden clips the footer. Popup is otherwise 420px wide × 560px tall.
Note: This looks addressed on the fix/popup-clipping-chrome line (switching to height: 560px; max-height: 100vh). Filing so it's tracked / lands in a release — please confirm the fix ships.
3. ⚠ 127.0.0.1:20128 isn't running
Symptom: The footer shows ⚠ 127.0.0.1:20128 isn't running.
Findings: This is produced in popup.js (~L575-589) via the popup_footerDown locale string when serverOnline is false, i.e. the OmniRoute gateway probe on port 20128 failed (background.js gateway guard ~L217-225). In our case the local gateway was genuinely down, so the warning is technically correct.
Suggestion (optional UX): The wording reads like an extension error. Could clarify it's the local OmniRoute gateway (e.g. "OmniRoute gateway not reachable on 127.0.0.1:20128 — is it running?") and/or link to start instructions, so users don't mistake it for an extension bug.
Environment: Chrome, extension v4.24.9. Happy to provide more detail or test fixes.
Reporting three issues observed with the extension (v4.24.9, Chrome). Grouped into one report; happy to split if you prefer.
1. Cookies are not detected automatically
Symptom: After logging into a provider site (e.g. ChatGPT), the popup does not show the session as captured until some network activity happens on the page.
Likely cause: Cookie capture appears to rely solely on the
chrome.webRequest.onBeforeSendHeaderslistener firing on anxmlhttprequest(seebackground.js:65-89). If the user just lands on a provider page while already logged in and doesn't trigger an XHR carrying the session cookie, no capture entry (cap_<provider>) is ever created, sopopup.js(~L901-902) shows nothing captured even though the user is authenticated.Suggestion: Add an on-demand/periodic read via
chrome.cookies.get/getAll(or thecookieStoreAPI) when a provider tab is active, so a logged-in session is detected without waiting for an XHR.2. Popup is very small / clipped
Symptom: The popup renders very small on open, with the footer clipped.
Likely cause:
popup.csssized the popup withheight: min(560px, 100vh);100vhunder-resolves during Chrome's initial popup layout, somin()picks the tiny value, andoverflow:hiddenclips the footer. Popup is otherwise 420px wide × 560px tall.Note: This looks addressed on the
fix/popup-clipping-chromeline (switching toheight: 560px; max-height: 100vh). Filing so it's tracked / lands in a release — please confirm the fix ships.3.
⚠ 127.0.0.1:20128 isn't runningSymptom: The footer shows
⚠ 127.0.0.1:20128 isn't running.Findings: This is produced in
popup.js(~L575-589) via thepopup_footerDownlocale string whenserverOnlineis false, i.e. the OmniRoute gateway probe on port 20128 failed (background.jsgateway guard ~L217-225). In our case the local gateway was genuinely down, so the warning is technically correct.Suggestion (optional UX): The wording reads like an extension error. Could clarify it's the local OmniRoute gateway (e.g. "OmniRoute gateway not reachable on 127.0.0.1:20128 — is it running?") and/or link to start instructions, so users don't mistake it for an extension bug.
Environment: Chrome, extension v4.24.9. Happy to provide more detail or test fixes.