punkypangolin

It does. As far as I can tell, it works exactly how it should. I've used Wireguard on a few different computers and … yeah. Looks totally normal If I have the time and this frustrates me enough, I'll eventually try to track it down and update this thread, in case anybody else has this same issue. Thanks again!

Sorry, Christian. Missed the notification and forgot about this. I'm running the latest of everything. Wireguard 1.0.13 (24), macOS 11.4. The empty items is strange, as I definitely have a Wireguard tunnel installed and active and functional. (I use it every day, and know it's working.) I get no response for this though: ❯ scutil --nc list ─╯ Available network connection services in the current set (*=enabled): So… my tunnel is somehow not showing up where it's expected? I've done a bit of googling and I'm not seeing anything obvious. Doesn't seem like an issue with your workflow, though, so that's good (for the workflow) Only thing I'm wondering is if there's some conflict with my other settings (Docker, Lulu, network profile / custom DNS, … maybe something else I'm not thinking about). But that'll be an exploration for another day!

@ChristianOlsen did this stop working with a recent version of WireGuard? When I attempt it now, Alfred seems to "forget" that it's a custom action, and it wants to search for the keyword. (It starts out with the Wireguard icon.) Debugging shows this: [22:51:00.130] Wireguard Control[Script Filter] Queuing argument '(null)' [22:51:00.221] Wireguard Control[Script Filter] Script with argv '(null)' finished [22:51:00.223] Wireguard Control[Script Filter] {"items":[]} Not sure what's changed on my end since it was working last. (And, unfortunately, I forgot I had it installed so haven't been using it much.) I tried deleting and reinstalling and get the same behaviour. Thanks!

This is fantastic. Thanks for building and sharing!