Hi @smutek - thanks for using Local! Welcome to the community.
Looks like we need to do some cleaning/combining on our end - there is an active thread in the support category for this issue. It is an issue specific to macOS Ventura. macOS 13 Ventura and Open Site Shell
I’ll merge the threads to keep convo in the same place, but our engineering team just spoke about this one again today actually. We believe it is an underlying bug in macOS 13 as it has popped up in a few other online communities that interact with terminal, not related to Local or WordPress. We’re seeing if there is a workaround and trying to follow updates from a bug report submitted with Apple.
In the short-term, a TL;DR of the linked forum post - install iTerm on your machine and then open Preferences > Appearance & Behavior and set your default Terminal to iTerm. Since this is specific to Terminal on macOS 13, this workaround has resolved the issue for other users.
O.k.
First; sorry for the late response, somehow I don’t get notifications and being busy with work made me forget to check myself;
Yes, I restarted the machine, about 4 times since my last post. (Love how macs stay stable without reboots for months on end) and it did not help.
but
I just upgraded to the latest version, saw the problem was still there, came back here, saw your reply, and tested it; rebooted immediately after removing the attributes, and now the open site shell link works as expected.
Hey all - just following up here before the thread resolves itself. To summarize the long thread…
This was due to a permissions change in macOS Ventura and how Local was launching Terminal. We changed our approach and released the fix in Local v6.7.1 (and patched in v6.7.2, as we broke non-Terminal shells…) but it is resolved!
If you still have any issues, please let us know, but this should be behind us.