Andrew

@fuksito Even more simple, just a Hotkey Trigger workflow object set to "Show Alfred"

@Jenkins macOS should automatically request permissions for the Automation tab where necessary. If this isn't happening, there could be an underlying issue preventing this from happening. When was the last time macOS asked for permission such as this? Was it recent? You could try resetting the Automation access tab. https://developer.apple.com/library/archive/qa/qa1906/_index.html In terminal, you can use the following command to only reset Automation instead of all: tccutil reset Automation Cheers, Andrew

@stylophile Alfred 4 hasn't changed in this regard compared to Alfred 3 and before... if another app is already using a specified combination, macOS will divert this combo to that app and Alfred (and Alfred's Preferences) won't even know this combo has been pressed (i.e. for you to set a hotkey in one of Alfred's hotkey fields). It actually acts as an inherent safety net to prevent a key combo from being registered twice, and causing undesirable behaviour. Having said that, not many apps will be registering system level hotkeys, so you may have an (accessibility based) app which is interfering with the combos before they are even distributed by macOS. Check the macOS Accessibility preferences to see which apps have access here. Also, perhaps try a new user account with Alfred to see if you are able to register more combos there? Cheers, Andrew

Basic question - have you tried setting an obscure combo which isn't used by any other apps, just to make sure?

@Koinseb if you update to Alfred's 4.0.2 pre-release, there is already a fix for this. Cheers, Andrew

@scaba have you tried just adding the symlink file type to Alfred's default results in Features > Default Results > Advanced?

@georgexsh try dragging the alias file to Alfred's Features > Default Results > Advanced to add the alias file as a default type Alfred searches for.

@Acidham "Browse in Terminal" will cd to the path you pass (or if you have the default terminal set, which I recommend if using Terminal.app, then it'll open the Terminal app to the specified path which is much faster). If you just want to run a terminal command, use "Run Terminal Command"

@xilopaint It's not quite that simple, many of the workflow objects have had updates adding additional features which make them no longer compatible with Alfred 3. Alfred 4 can happily load Alfred 3 workflows, so if there is an absolute need for a workflow to work in Alfred 3 and Alfred 4, you'll need to create it in Alfred 3. Cheers, Andrew

@Acidham Alfred shouldn't be adding cd to the front of the query. Could you please clarify a little, as I don't understand this: What script do you have shown when you select Custom? By default, Alfred has this one: on alfred_script(q) tell application "Terminal" activate do script q end tell end alfred_script Cheers, Andrew

If you update to Alfred's latest 4.0.2 pre-release b1086, could you let me know if those icons are still missing? Thanks, Andrew

@Savior If you update to the latest 4.0.2 pre-release b1086, I've now made the hat in the Alfred window a draggable zone too, so you can easily move Alfred's window around from this

@nikivi if you update to Alfred's latest 4.0.2 pre-release b1086, you should get the behaviour you're after. Could you let me know?

@Michael Cordell The error message mentions Chrome - Have you tried downloading it with Safari? I've just double checked the download and it's fine.

I haven't installed Catalina yet (I also generally recommend against anybody installing a beta OS this early if it's their main Mac), but I have made a few tweaks for the next 4.0.2 build which should get these icons back again. I'll likely out this build tomorrow. Cheers, Andrew