On macOS 26 (RClick 1.7.2), "Open With" and New File do nothing in a folder that has not been added under Settings → General. Per #99 and #101 this is the expected sandbox model: actions only work in authorized folders.
The real problem is the lack of feedback. The menu items appear, clicking them does nothing, and there is no hint that the folder must be authorized first. checkPermissionFolder(), which would alert when no folder is authorized, is commented out in GeneralSettingsTabView, and the open path's errors only go to print(). So from the user's side the feature looks simply broken.
A one-time prompt along the lines of "authorize this folder to use RClick here" would turn a whole class of "doesn't work on macOS 26" reports into a clear, self-service action.
Environment: macOS 26.5.1 (arm64), RClick 1.7.2.
On macOS 26 (RClick 1.7.2), "Open With" and New File do nothing in a folder that has not been added under Settings → General. Per #99 and #101 this is the expected sandbox model: actions only work in authorized folders.
The real problem is the lack of feedback. The menu items appear, clicking them does nothing, and there is no hint that the folder must be authorized first.
checkPermissionFolder(), which would alert when no folder is authorized, is commented out inGeneralSettingsTabView, and the open path's errors only go toprint(). So from the user's side the feature looks simply broken.A one-time prompt along the lines of "authorize this folder to use RClick here" would turn a whole class of "doesn't work on macOS 26" reports into a clear, self-service action.
Environment: macOS 26.5.1 (arm64), RClick 1.7.2.