bwoodruff

Hello! 👋🏻 One of our founders, Dave, has posted an update on our progress and current thought process on this type of integration with Alfred and other tools looking to integrate in similar ways with 1Password. You can read that update here: https://1password.community/discussion/comment/632452/#Comment_632452 Thank you all for your continued patience as we continue to work with Alfred and other developers to make this the best experience possible. Ben

Hi folks, Ben from 1Password here. Indeed; I can't imagine there is any significant technical hurdle here. One of our Apple developers commented on the subject: https://1password.community/discussion/comment/607254/#Comment_607254 I'm afraid I don't know exactly when we'll be able to work on this, but we love Alfred (I've got a Legendary Supporter Powerpack license) and it is definitely on the radar.

Ah! Okay, it was outputting to STDERR. Adding 2>&1 fixed the problem. Thank you both!!

Hello, I'm trying to build a fairly simple workflow that: 1. Finds all private SSH keys in the ~/.ssh director 2. Runs `ssh-add -K` on each of them 3. Sends the output of the commands run to a notification Here is what I have: The problem I'm having is that `{query}` appears to be blank after the script runs as the notification title says "ssh-add" as intended, but the text of the notification is blank. Can anyone help please? Thank you. Ben

Ah fair enough. Thanks!

This, unfortunately, does not seem to resolve the problem I'm having. I use Alfred's clipboard history feature extensively, but I find I'm unable to make use of it on my 2nd screen. I tried both the "show Alfred on" mouse and active screen options. When I try to do a CMD+Opt+C on the 2nd display, despite the fact that Alfred appears on the correct screen, the filling from the clipboard history *always* happens on the primary screen. Is there a setting I'm missing, or is this a bug? Alfred v2.5.1 on OS X 10.10.1 on a 2012 rMBP with dual displays (one connected via Thunderbolt the other by mini-DisplayPort). Edit: I stand corrected. It is not *always*. It only happens with Chrome, when I have a window on both the main display and the 2nd display.