TimeDelta

I figured out that restarting Alfred temporarily fixes the issue. Also, when I quit Alfred, I notice that a bunch of empty stdin files pop up in Sublime Text

Oops, didn't realize there was a better place to post this (Bug Reports). Not sure how to change that now though.

So I have a workflow set up with a script filter triggering a "run script" action. The (/bin/bash) script action is set to escape backquotes / dollar signs, run instances sequentially and contains this: echo entered alfred.workflow.action.script >&2 ./process_command.sh {query} When the script action gets executed, the Debug pane (set to log all information) shows this: [iNFO: alfred.workflow.input.scriptfilter] Processing output 'alfred.workflow.action.script' with arg 'restore sa ' At first, I thought I just screwed something up, so i set up a hotkey trigger to go directly into the same script action, but it still only yields this: [iNFO: alfred.workflow.trigger.hotkey] Processing output 'alfred.workflow.action.script' with arg 'restore sa' The weird thing is that it used to work just fine. The only thing on my system that's changed in that time is that I installed the newly released public beta update for El Capitan - 10.11.1 Beta (15B38b). I have randomly gotten it to work again after first experiencing this issue (not sure how) but it broke again soon after. In case it helps, here's a link to the GitHub repo containing my code: https://github.com/TimeDelta/session_archiver

So I tried using the direct to ip connection with port forwarding via my router. Works perfectly now. Thanks!

I just have an all-in-one router/modem. I've been playing with it some more and it seems like the first time I connect it takes 5-10 seconds and then if I lock my phone and unlock it again within a certain amount of time (I don't know exactly how long), it connects almost immediately but if I wait a while before opening the remote again it takes 5-10 seconds again. I'm not sure why this would be happening. I'll try connecting straight to the IP address later on today to see if that makes a difference and post the result here. Do you have any thoughts on the other annoyance (being able to run a command from anywhere with an internet connection)?

Perhaps an option to allow the remote to stay connected when the display is sleeping then to address the first issue that I mentioned.

I just recently bought Alfred and the remote to go with it. First, I should say that I love the remote. It is a great idea but I've noticed two annoyances with it. First, there is a major limitation in that it can only be used if you're on the same WiFi network as your computer. It would be more useful to be able to run workflows, etc. from anywhere (e.g. using my cellular data connection to issue a command when I'm not home). Second, when I'm at home using it to control music or a movie or something, it's pretty annoying to have to wait 5-10 seconds for the remote to connect before I'm able to do anything, especially because i'm usually only doing one action each time it connects. The option to "prevent device from sleeping when the remote is connected" indirectly addresses this but leaving my display on constantly drains my phone battery very quickly. For the iPhone remote app (not sure if there's an Android version), both of these problems can be addressed by using the new option (as of Yosemite I believe) to sync app files between mobile and desktop via iCloud for a more integrated experience. This could be used to pass messages back and forth in a way that circumvents the need for a local network and the need to wait for a computer to respond before issuing a command (you could use an "update remote layout" button instead of automatically updating the remote each time it connects to a computer). I'm not sure how you would address this for an Android version of the remote though. Maybe by adding the option to use Google Drive or Dropbox or something to automatically push the messages between apps. Please and thank you, Bryan