gloogloo

New since shared here (currently on v1.0.2): We got a 'copy next' snippet which comes in handy if you are in Alfred's bar and want to use an item from your stack/queue. There's also a hotkey & snippet to copy or paste the previous item in your stack/queue in case you want to process in the opposite direction. There's a new clipboard history filter, to manually add individual items from Alfred's Clipboard history (last 30 items) to your stack/queue. Press the FN modifier in the main menu "Add from Clipboard" option. More modifier combinations have been added to the readme section that covers this. The new clipboard history filter is an implementation based on THIS CODE (which grabs the clipboard items from Alfred's database), but in PasteFlow, we also got some modifier options. With CMD, for example, you can add an item and loop back to the same menu (with the list of clipboard items) to add more to your stack/queue. I just find it convenient and couldn't do something like this directly on Alfred's Clipboard manager. I've added a custom hotkey for users to quickly jump to this new Clipboard History filter. There's also the new `clipFilter` argument that works for the external trigger to open this view. There's been a few bug fixes too. You can always grab the "Latest Release" from Github.

PASTEFLOW A Paste Stack & Paste Queue for Alfred. Pin & Reuse Text. ~ Full Documentation ~ | ~ Latest Release ~ | ~ Video Overview ~ REQUIREMENTS This workflow uses Alfred Clipboard history. You don't have to be using Alfred as your main Clipboard Manager, just make sure you don't turn this feature off WHAT IS IT PasteFlow is a handy paste stack (or paste queue) for Alfred. It lets you create a list of pinned text items that you can organize, edit, and use in different ways. Ever needed to copy text from various places and put it all in one final spot? PasteFlow makes this easy. No more switching back and forth to copy and paste one item at a time. Save time and stay in flow by doing all your copying first, then pasting later when you're ready. Since your items are saved in an actual list, you can even take a break, copy other things, and come back to your stack whenever you want. HOW TO If you're already familiar with paste stacks, you can start using PasteFlow right away with its default settings. Here's how to get started: Add items to your stack: Select text and use Pasteflow actions on them. Set up your preferred hotkeys (green color-coded hotkeys are the most basic/essential). Use PasteFlow's keyword to add items from your Clipboard to your stack. Process your saved items The easiest way to do this is to set up a hotkey (in green), but you can also use PasteFlow's keyword directly on Alfred's bar. Paste items to your current window Copy items back to your clipboard View & edit your stack: Set up hotkeys (red-coded hotkeys show your entire list) Enter "Selective Mode" from Alfred's Bar using PasteFlow's keyword Use Textview Mode (type :View with PasteFlow's keyword) That's all you need to get started! But if you want to explore more, PasteFlow has lots of other useful and powerful features. SOME FEATURES: Items can be added at the top (use it as a stack) or they can be added at the bottom (as a queue). Similarly, you can process from the top or the bottom. Selective processing view offers a very close experience to a traditional pastestack. You can move items up or down your list, clear them, edit them individually, etc. Your list can auto-clear itself (grabbed inspiration from Sequential Paste for this one), or you can set it in a custom path and ignore the timeout. Without a custom path it will go to the workflow's cache folder. You have options for after processing your items to restart or do nothing (you can set your items to auto-clear when processed or you can loop through your list). You also have actions like to do right after pasting (insert a line break, comma, space, press tab). In the main menu you can always see your entire list with CMD L on any item. Plus there's a Textview mode (access it with :View) and there's also selective mode which shows individual items with CMD L. You can select a list of items and auto split + insert to your stack. There's more features and explanations. Everything is documented over at Github. I grabbed some inspiration from Sequential Paste, but also from the paste stack feature from Paste, and the Paste Stack/Queue from CleanClip (which IMO has the best paste stack I've tried). I recently have tried to make more use of Alfred's clipboard management features and I realized I was missing something like this, so I created it. I'm exited to share PasteFlow here and hope many of you also find it useful.

I'm working on a workflow that allows users to trigger options with modifiers. I noticed the FN modifier doesn't work in the new Text View, while all other modifiers function properly. I also tested the FN modifier with different action blocks (keyword triggers) to confirm the issue isn't with my keyboard. Just reporting here. I'm on the latest Alfred 5.5 [2257]

A few important updates for this workflow have taken place since I posted it. Taptix can now play WAV files (24 bit & 16 bit). This allows for better audio quality and faster speed, since these do not need decompressing as MP3s. MP3 files are still supported and will be used as a fallback for custom sound packs if no WAV files are found. All default sound packs in the workflow have been rebuilt using WAV files. Implemented some thresholds both for key down & key up events which should be helpful for users that use this workflow on a laptop and for users that use macros/automations. Basically, key down & key up sounds need at least 10 milliseconds between them—otherwise we only get a key down sound. Also, when keys are pressed down or released at the same time they will produce a single key down or key up sound. This should only make the sounds much more cleaner, and avoid the playing of more than one audio files at exactly the same time (which was sometimes resulting in a sudden higher volume). There’s been several under-the-hood code optimizations which, with all the above, make the workflow feel much more snappier and with less lag. The workflow can now load sounds from multiple paths at the same time, which allows for a new “Extended Sound Packs” option in the configuration. This makes it easier for users to to be able to choose their own personal sound packs in addition to the default ones. Users can now hold CMD on the “Activate/Deactivate Taptix” option in Alfred’s bar to quickly jump to the Workflow’s configuration. I’ve incorporated the auto-updater script for users to easily keep this workflow up to date. LATEST RELEASE

Thank you so much @vitor for the heads up. It took me a bit of researching but finally compiled the binary for both architectures, so it should now work for both Silicon and Intel. Also, thanks for the note about Sequoia... I'll add a note in the readme. On regards to the video, every time I click there's a "ripple effect" that comes from the screen recording app (Screen Studio). I also have a white indicator/highlight which comes from the app Presentation Assistant, but I think you are asking about the ripple effect. The Hyper Actions is one of my submenus in Kando. Kando is a pie menu that I have setup for my mouse so that I can perform custom actions (launch apps, manage windows, macros, etc) with my mouse alone. I usually prefer keyboard but it's still useful in those cases I am on the mouse and don't want to switch device. I think on the video I used it for hiding Alfred temporarily. Thanks!

TAPTIX Mechanical Keyboard and Mouse Sounds for Alfred ~ Full Documentation ~ | ~ Latest Release ~ | ~ Video Overview & Setup ~ REQUIREMENTS This workflow supports Fuzzy Search (thank you for this code!). This is useful in case users decide to make a long list of custom sound packs. This is the first time I'm incorporating this in a workflow and I'm not familiar with Python at all. I have no clue if users need to install anything for this to work. My guess is that it should work out of the box, but any issues let me know. This workflow includes a small Go app. I'm not an "official developer" so users need to authorize the app for it to work. Other option is that users can compile it themselves from its source code. FEATURES Realistic sound playback for key presses (up and down) and mouse clicks. Custom sounds for spacebar and return key. Randomized sounds for other keys to enhance realism and simplify custom sound packs. Customizable settings: Keyboard and mouse sounds. Global and per-device volume. Mute status per device. Do not disturb mode. Easy access to settings via Alfred's search bar ("tt" keyword), keyboard shortcuts, or external triggers. Advanced: Create custom presets by modifying multiple settings at once using external triggers. HOW TO 1. Upon installation you must AUTHORIZE Taptix for it to work. 2. The welcome screen configuration settings are used each time Taptix starts. I suggest you keep the defaults at first and change them later—once you familiarize yourself with how the Workflow works and your preferred sounds/settings. 3. The most straight-forward way to use Taptix is with its keyboard: "tt" or "taptix". The menu options are self explanatory, but there’s two things you must know: Fuzzy search is supported (e.g., "tt sk" for "Set Keyboard Sound"). Hold CMD or OPT when selecting "Set Volume" to adjust keyboard or mouse volume separately. There are customizable hotkeys, external triggers (with lots of possible arguments, which provide absolute control of the workflow even without interacting with Alfred's bar), and there's the possibility of creating custom sound packs. If interested, please take a look at the full documentation over at Github.

Thanks @vitor, I was just trying to update an older workflow where I did realize I was incorrectly using the Environment Variables set in this way, but I was really curious as to what was going on (because IMO, it should have still worked)... that's why I tried to figure out what was causing it. I've since updated my workflow to return normal variables in JSON form. So, this is not something I need right away, but I still think it's something that would be handy to have working properly for other use cases. Thank you @FireFingers21, it's great to know about the "reload workflow" workaround.

I just found what seems like a bug when setting an environment variable from an external script. I have created a “Test” workflow which you can download below. Basically, I have a script action which loads a .js script externally. The script is loaded from within a bash script action as: /usr/bin/osascript test.js "$1" At first, the Javascript sets the environment variable correctly. I can use the environment in other action blocks. HOWEVER, the moment that I add ANY block in the configuration builder, I can no longer use it in other action blocks, at least not always—even though it seems correctly set, since I haven’t changed anything. Test Workflow A video showing the bug in action. I am not using Alfred preferences on any cloud service. Alfred 5.5 (2257) Sonoma 14.5

In case anyone stumbles upon this workflow. For some reason I can't edit my original post but just a quick note to mention that Kiki now supports Anthropic's models (Claude), Whisper AI, and can also be set to use a custom API Endpoint, among a few more things. Updates and full documentation can be found over at GITHUB

@iandol I've just released a small update making the main request script a separate file. Feel free to add what you need. Man, I'm actually very close to being code illiterate and most of what you see in there both in bash or Javascript came from GPT 4 itself, so any help is welcome and it's great if you can contribute adding something that helps you or others.

Hey @iandol, thanks for trying Kiki out! I saw the feature request for local LLMs. I haven't really looked into it, but have added it to my to-do list to check this out and see if I can consider it in the future. Adding custom API endpoints may not be too complicated but I'm an absolute beginner at this so even "simple" things do end up eating a lot of time. Oh, and Kiki doesn't stream replies yet. It's one of those things that I'll try to do if I can incorporate it with the new text view. For the most part I've built this on the go, adding the features I personally needed, and just trying to adapt them in a way that is also useful to others. Seems like I still have a long way to go. Even though I know very little coding and about building Alfred workflows, I think this workflow has ended up being a bit too complicated for the average user. I mean, it "can" be if the user wants it to, or they can give it a very basic use, but the length of the documentation alone is probably enough to scare some away. Still, I think Kiki offers some flexibility and features I haven't seen in any other LLM workflows. Would love to be able to submit to the Alfred's gallery, especially for the ease of offering updates, but it seems like submissions are closed. Thanks for checking this out!

I made Kiki, a workflow that works not only with Open AI but also with OpenRouter models (which includes Claude). I have actually already incorporated access to Anthropic's API but haven't gotten around uploading this latest version (I need to update the documentation since I also incorporated Whisper). The update should be up sometime this coming week. It's not as pretty as Alfred's new Chat GPT workflow (still haven't figured out how to use incorporate the new text view or if I should incorporate it at all) but it's super versatile.

Kiki AI-Powered Chat & Text Tools For Chat GPT and OpenRouter's Models A short video showcasing some features. REQUIREMENTS: OpenAI or OpenRouter API Token Jq: Can be installed from Homebrew This workflow is specifically designed with the following features in mind: Quick chats initiated from Alfred’s command bar: These chats start in the command bar of Alfred and continue as AppleScript dialogs. Create and use presets for selected text or user input: Customize prompts, system role, temperature, and other settings per preset. This feature can help with grammar correction, translations, rephrasing, tone adjustment, smart text transformations, idea generation, and much more. Chat initiation options with the use of modifiers from Alfred’s command bar: These options include selecting an alternative model, an alternative system role or "persona," pasting results in the frontmost window, and preserving or resetting existing context. Easy continuation of previous conversations: Seamlessly continue previous conversations by using Alfred Universal actions on existing context files. Trigger presets on text using hotkeys, snippets, or external triggers: Activate presets on text using hotkeys, snippets, or external triggers for faster results, without needing to use Alfred's command bar. Markdown Chat: Enjoy the convenience of making AI requests directly in your preferred markdown text editor. Customize the chat settings through presets included on the header of your notes according to your preferences. SCREENSHOTS A few things I must mention: I have written an extensive documentation over at Github. I may have gone a bit overboard, but this workflow can be as simple or as complicated as users want it to be. My coding skills are very basic, so most of the code used to create this workflow came out of Kiki itself. There are some workflows that are very powerful in using all that OpenAI's API has to offer, but Kiki doesn't try to do everything. This is a tool that shines as a utility for everyday text-related tasks. Because of that, I currently do not have plans to integrate it with image generation, vision, etc. Instead, I welcome any ideas on how to make this better at what it does. I have tried to work around limitations, and I've tried to make this workflow as customizable as possible, but I know it could probably be better. If you encounter any bugs that you can reproduce please feel free to comment or let me know. Honestly, I'm a total beginner at this, but will be happy to help if I can. Lastly, I hope I am not asking too much by requiring users to install Jq. I know that Alfred workflows that make it to the gallery do not have to deal with this, but it seems gallery submissions are closed for the time being. I also know that not every user wants to deal with the creation of presets using JSON files, do you have any idea on how to improve this? It's my first workflow submission to this forum. I'm not sure of what I'm doing here (or on Github), but I hope you give this a try and hopefully find it useful. GITHUB | DOWNLOAD

Perfect thank you so much, I don't know how I missed this.

I know there is the setting under Settings/Universal Actions that applies for all workflows, but if I plan to share a workflow I cannot expect everyone to have that unchecked. The thing is that I am working on a workflow that has several script filters and—for the most part—they do not work as universal actions. They can only receive the listed items as arguments, nothing else. Especially since I like to have the "Alfred Filters Results" option checked on my script filters. This results in having Universal Actions that seem broken, because they are there listed with all the others but basically are unusable. From some testing it seems like if I don't give my Script Filters a keyword they won't be listed as Universal Actions but I'm wondering if there's any other way? I've tried searching and reading all the documentation without success. Any help is appreciated. Thanks!