><i>Any links using those schemes when clicked, would open the MacOS terminal to perform the corresponding action.</i><p>I'm unclear which of these are being described:<p>1: when printed and clicked, they may be handled by the terminal, and the terminal's handling allows more behaviors than it should, allowing code execution<p>2: when printed, these urls are <i>automatically</i> executed by the shell, allowing code execution<p>Neither are good of course, but they're different levels of badness, and I feel like I must be missing a single critical word somewhere to be able to figure out which it is.<p>---<p>That said, oh boy I do not want this:<p>><i>Most terminal emulators these days allow using Osc 8 to directly generate hyperlinks from arbitrary text.</i><p>Is there a standard way to disable it? That sounds awful, terminals don't have even a small fraction of browsers' malicious-link-defense mechanisms (as demonstrated). I <i>always</i> want to see the full url in a terminal.