Hello @kalaschnik

That could be something quite useful, but due to the loading performance reported, mostly due to the Alfred JSON and keepassx limitations it would be increasing the loading time.

I'm thinking if to try to refactor the code using some other language implementing some kind of cache of the keys for the database to speed up the listing and look up. But that can raise some security concerns so I want to think about it and also I will have to look for time to do it.

Thanks for reporting improvements :)

You may work around performance issues by introducing a sub command. For example kpass db1 for querying db1, etc. Thanks for the response.

You could Edit the workflow and copy & paste the kpass script filter

In the kpass Script Filter edit the:

• keywords with something like: kpass_db1
• At the top of the script add the following line: export database="db1"

In the bin/bash Script Filter add:

• At the top of the script add the following line: export database="db1"

This will make a command for the specific database, I think this will be a good workarround for your functionality

That would not survive an update though?

I tried to tweak it by duplicating (and renaming) the workflow, editing the plist file manually and manually adding a Keychain item.

But for some reason it briefly displays "Please loading database..." but with no results. Everything seems to work fine, but no results are shown. The first workflow still works fine and as expected.

If we could get it to work like this, I guess that would be a nice option until we may get the multiple database support.