A link in the profile you choose

A message arrives with a link, and the account it has to open as is not the one your everyday browser is signed into. By hand that means finding the profile in the list, starting it, waiting for it, and pasting the address into a fresh window.

Four steps is enough friction that people stop doing it. They glance at the link in whatever browser is in front of them, and the account that was supposed to see it never does.

Here it is one action on the profile you point at. Everything the page then reads comes from that profile and nothing else.

The entry sits in the profile's own menu, between Test fingerprint and Duplicate. Right-click a card or a row in the list, or use the three dots on the card.

Choosing the account first is the whole design. You are never typing an address into a window and hoping it lands in the right place.

1. 1

   Pick the profile

   Open a link here is a line of that profile's menu, so the account is chosen before the address is.

2. 2

   Paste the address

   A small window asks for the link and names the profile it is about to open in.

3. 3

   Read the answer there

   A refusal stays in that window with the real reason, and a success closes it.

A person pastes this address, so the app checks it instead of trusting it. Anything that is not an ordinary web address is refused by name.

The reason is that the page opens with the profile's own rights. An address that reads files or runs code would do it from inside the account you were trying to protect.

The account does not have to be running first. A closed profile goes through the same launch door as the Run button, with every gate that door has: the proxy, the fingerprint, the busy lock.

That last gate matters most. A profile a colleague holds on another machine refuses the link too as long as your account is reachable, and the refusal names the machine.

A profile already at work is never restarted for this. The page opens beside what is there, assembled from the same recipe that launch used.

A second page that skipped the proxy would put the account on the open internet from your own address, and a phone profile answering as a desktop is a contradiction any site can read at once.

What that looks like on screen depends on the engine.

A link that does not open is better than a link that opens somewhere you did not expect. Each way this can fail has its own sentence in the same small window.

A launch that did not happen passes its reason through whole instead of being replaced by a general phrase.

• Not a web address

  You are asked for one starting with http:// or https://, and nothing opens anywhere.

• Held on another machine

  The refusal comes from the busy lock and names the machine that is holding the profile.

• No seat left

  The ceiling on open profiles is reached, and the line tells you how many are open.

• The page did not open

  The profile is up and the address was not accepted by the engine, so the line names the profile.

Nothing about the link travels upward. We do not receive it, count it, or learn the domain.

A list of the links other people send you would be worse than any fingerprint leak. So this action has no road to our server at all, and a stand holds it that way.