When opening a link to a website that requires a cookie to access and otherwise redirects you to a login page (such as links to private GitLab repos), opening the link via OpenLinkWith results in landing on the login page, despite the browser session being authorised.

I've also noticed that OpenLinkWith regularly has a noticable delay before showing the list of available browsers; showing a spinner. Could it be that it's connecting to the website to be opened in another app in any way?
Manifesting my suspicion further is the fact that OpenLinkWith reproducibly has a consistent rather lengthy loading time (with spinner) when you are offline; suggesting it's waiting for a timeout.

As a user, I want OpenLinkWith to pass through the link unaltered without making any network connections so that I can open links that only work in my browser session.
As a user, I want to be given the choice of app as fast as possible without noticeable delay.
As a user, I want the URL to be touched only when URL cleaning is enabled.

Redirect resolution can be a desirable feature in some situations. Enabling it unconditionally results in bad UX as described here. It still is a useful feature however IMO. I believe that a button in the pop-up that cleans up and resolves the redirect would be a better approach.