Problem
Some applications (CLI tools, auth flows, etc.) automatically open links via the default browser handler. Since Browserino intercepts these, the popup appears — but if you miss it, dismiss it accidentally, or the window loses focus, the link is gone. There's no way to recall it.
This is especially annoying with OAuth/SSO auth callbacks where a service opens a one-time login URL automatically, and you need to act on it quickly.
Proposed solution
Add a way to reopen (or re-show the Browserino picker for) the last received link. Two possible UX options:
Global keyboard shortcut (configurable in Settings) — e.g. ⌥⇧T — that re-triggers the Browserino picker with the most recently received URL.
Menu bar item — "Reopen last link" action/button in the Browserino menu bar dropdown.
Ideally, Browserino would keep a small ring buffer of the last N links (e.g. 3-4) so the user could pick from recent history, not just the very last one.
Additional context
The link history should probably be ephemeral (in-memory only, cleared on quit) to avoid privacy concerns. Persisting to disk could be an opt-in setting.
Problem
Some applications (CLI tools, auth flows, etc.) automatically open links via the default browser handler. Since Browserino intercepts these, the popup appears — but if you miss it, dismiss it accidentally, or the window loses focus, the link is gone. There's no way to recall it.
This is especially annoying with OAuth/SSO auth callbacks where a service opens a one-time login URL automatically, and you need to act on it quickly.
Proposed solution
Add a way to reopen (or re-show the Browserino picker for) the last received link. Two possible UX options:
Global keyboard shortcut (configurable in Settings) — e.g. ⌥⇧T — that re-triggers the Browserino picker with the most recently received URL.
Menu bar item — "Reopen last link" action/button in the Browserino menu bar dropdown.
Ideally, Browserino would keep a small ring buffer of the last N links (e.g. 3-4) so the user could pick from recent history, not just the very last one.
Additional context
The link history should probably be ephemeral (in-memory only, cleared on quit) to avoid privacy concerns. Persisting to disk could be an opt-in setting.