Know what reaches Browter.

Links inside a browser stay in that browser

Clicking a webpage link normally navigates the current browser or opens another tab there. That navigation does not call the Windows default HTTP/HTTPS handler, so Browter does not receive it. Alt + Q can arm a choice, but cannot turn an internal browser click into a Windows handoff. Shift + click may instead perform the browser’s own action, such as opening another window.

For an occasional exception, copy the link address and paste it into the browser/profile you want. Browter 1.0 does not include a browser extension or an Open clipboard link command.

Embedded browser views and app-specific preferences

In-app previews, embedded web views, and apps that launch a specific browser directly can bypass Windows defaults. Browter cannot redirect navigation that stays inside another application. Use an Open in external browser action, or configure the source app to use the system/default browser where it offers that option. This helps only when the action actually hands the address to Windows.

VS Code: integrated views versus external links

VS Code is not categorically incompatible with Browter. Its integrated browser navigates within VS Code, while external links can use the operating system’s default browser. Current VS Code versions open localhost links in the integrated browser by default.

1. In VS Code Settings, disable workbench.browser.openLocalhostLinks to open localhost links externally.
2. Leave workbench.externalBrowser at its default rather than selecting a specific browser executable.
3. Set Browter as the Windows HTTP and HTTPS default, then test the external handoff. A Simple Browser, extension preview, or webview may still keep its own internal links.

See VS Code’s integrated-browser and external-browser documentation ↗. Controls vary with version and extension; these settings do not make every preview link external.

Profiles and accounts need your attention

Create profiles in their browser, then discover and test them in Browter. A display label does not determine the executable or profile arguments, guarantee the right website login, or provide security isolation. Portable browsers, custom data directories, moved profiles, and managed policies can require manual configuration.

Shortcuts, full-screen apps, and timing

Another app or Windows may use the same shortcut. Change it in Settings → Hotkey. Gaming mode suppresses selection shortcuts; automatic full-screen detection can affect presentations and other non-game apps too. Windows permissions and managed-device rules can affect input handling in elevated applications. Test the source apps you rely on.

Shift + click depends on Shift being detected during the link handoff. Apps that delay the request or handle the modifier themselves can behave differently. An armed choice expires after its countdown; the default is 12 seconds. Increase it in Settings if needed.

Explicit selection and supported requests

Browter 1.0 has no automatic rules that assign domains or source apps to browser profiles. HTTP/HTTPS links and supported local HTML files need their Windows associations to reach Browter. Custom protocols and arbitrary files are not automatically browser requests. See system and discovery requirements.

Transparency and local data

The wheel has translucent tint and reflections, not a blurred desktop. Appearance changes with the background, theme, Windows transparency, and high contrast. Local settings, history, and recovery files are not an encrypted vault. Turning Recent links Off stops that history feature but does not stop recovery records or diagnostics.

Troubleshoot a handoff ↗ · Read retention and deletion details ↗