zeitlings

Just related to the cosmetics of your workflow, but I noticed you're using the square root math symbol as a check mark, and for some reason that irritates me 😅 Anyway, there are a few neat alternatives: ✓, ✔, ✅, ☑, 𐄂

Perhaps just a typo, but it's shift+cmd+G, and yep, that one is a valid shortcut. (Btw. it's the same for Finder windows, i.e. the shortcut is for a generic "Go to Folder" utility.)

alfred://customsearch/perplexity.ai/pai/utf8/nospace/https://www.perplexity.ai/search?q=%7Bquery%7D I think this is just a handler to set up custom web search, i.e. intended to be used only once. Once you do that, you should be able to to run searches on the perplexity website by writing "pai your query" in Alfred and hitting return. If you're setting up a workflow, the URL you enter into the Open URL Object should just look like this: https://www.perplexity.ai/search?q={query} If your hotkey is set to use the selection in macOS as argument, triggering it will open the perplexity website with whatever text you have currently highlighted.

Thanks 🤗 Is it? I noticed that the sorting looks wrong when viewing all releases, do you mean this? But alpha.2 should be set as the latest release. So yes, alpha.2 has some fixes and changes over alpha.1. However, mind that the problem with the data directory not being created is not fixed yet.

Thanks for the error message. For a quick fix, you can try replacing this [[ -d "$archive" ]] || mkdir "$archive" with this [[ -d "$archive" ]] || mkdir -p "$archive" here

Only messages that the model deems to require real-time information will elicit a detour through exa.ai. OpenAI dubbed this tool- or function calling. I caution the model to be extremely conservative about calling the function, so ideally it should only happen when really necessary. Whenever it does happen, you will notice that a "Searching" notification is injected into the conversation! This is when the external API is contacted, otherwise exa sees nothing, and even then it doesn't see your message, but only a search query constructed by the model to get the information it needs.

Yeah, the solution is a trade-off. I've added the option to explicitly preserve unnamed windows to compensate for those cases. By default, these windows are hidden, but they can be made visible if necessary, at the risk of potentially mixing in other unwanted windows. Given that unnamed windows are the exception in my experience, I think this should be an adequate solution for most situations.

Hey @dood, I did some digging and found that Arc does some strange things: Each modal or popup seems to be created as a unique window. The same appears to happen when a "booster" is added or has been added - but this behavior is inconsistent. These are not valid windows, although their properties suggest otherwise, but fortunately most of those windows are unnamed. A small caveat is that sometimes the unnamed Arc windows could be considered valid, e.g. when opening the configuration of an extension. Anyway, I've modified the code so that you now have to explicitly opt in to keep unnamed windows. This seems to catch most if not all of the invalid Arc windows. Also note the new hidden environment variable to blacklist specific window names if necessary. v1.3.0 Added configuration option to explicitly preserve or dismiss unnamed windows Added hidden environment variable ignored_window_names to blacklist window names as an additional failsafe Note: Enter the names as a comma separated list

I am reasoning about an extensible "Inference Task" configuration scheme for my GPT workflows. Such a "task" defines among other things the system prompt, the parameters and the desired behavior how to handle the result, e.g. whether a result should be pasted into the frontmost application at the end or just copied. Concrete, simple examples are definitions for Universal Actions to correct the spelling of text, change the tone, or create summaries. Another use case would be a configuration for a chat session that effectively turns the current session into a translation engine or an etymological dictionary. And yet another use case, and this would require the key combo dispatches, is "snippet triggers". If the predefined combos could be evaluated in one go, it would be possible to define very specific application purposes. For example, in text editors actions could be configured to select only the last paragraph as the target for the task (⌥⇧↑, ⌘C, →, ↩, ↩), or the entire page, or actions could be primed to react very specifically to certain applications (e.g. Logseq). If this were possible via Alfred, I wouldn't have to rebuild the entire NSEvent simulation just for that, i.e. I wouldn't probably just drop that whole part. 😄 I hope that makes sense, and granted, this may be bit niche. But I figured, since the core functionality already exists, maybe it's not such a stretch to ask. If the internal implementation doesn't allow for an easy implementation, so be it~ As for the delay issue, maybe an approach similar to that of the "simulate typing text" automation task would suffice? Fast, medium, slow dispatch speed. If you're interested, I'd be happy to show you the drafts of the configuration scheme to give you a better idea of what's going on, or if you're curious about pkl (github), which I'm playing with to set it up.

You are welcome! This is just to more conveniently access the environment variable '${alfred_workflow_bundleid}' and the argument.

This sounds like an addition that would fit into [Extra Automation Tasks > Keyboard Simulation]. The idea is to pass in an array of string sequences that will be evaluated as a chain of "Dispatch Key Combo" objects. Example input: [ "⇧⌘←", "⇧↑", "⇧↑", "⌘B" ] That way we could reduce complexity in terms of individual components present on the canvas and programmatically define key combos that require more than one dispatch.

https://karabiner-elements.pqrs.org/ What I do is map a "hyper" modifier + hjkl to the arrow keys. So no, Alfred has no native vim mode.

You can just manipulate an environment variable to switch through different states. https://transfer.archivete.am/E1GxG/Demo | Conditional Switch.alfredworkflow

I've just checked all the possible ways to start a new chat, and they all work on my end. (Without more information, I can't infer where it stopped working for you or why.) Don't forget to keep an eye on the debugger to potentially identify any problems more easily. Sure, what's the problem?

sigh thanks. Fixed.

Sure, there are two ways that I see with only the objects we've already used. 1. Directly set and format your rich text in the "Copy to Clipboard" utility (that one actually does support rich text). 2. Just check out the "Dispatch Key Combo" chain and extend it to whatever you need the result to be. https://transfer.archivete.am/3ACFY/Test | Apple Notes Snippet 2.alfredworkflow

NoteCmdr looks neat! Coincidentally, I just stumbled over another extension today the author wrote, and it looks like he is using Apple's Accessibility API to "hack" into Apple Notes. But it looks like nothing that fancy is necessary for your use case. I just tested the approach with dispatching key combos and it does the trick. https://transfer.archivete.am/10YNHX/Test | Apple Notes Snippet.alfredworkflow

The problem is that those check list bullets are no ordinary unicode characters, but more complex custom objects internal to Apple Notes. You'll notice that you can't even select them. If you copy a checklist, however, Apple Notes converts the checklist bullets to this markdown notation:- [ ] Trying to expand those will however also not automatically convert them to the interactive checklist objects. I'm afraid that this won't work with regular text expansions. You can however try to create a custom workflow that inserts your snippet and then dispatches some key combos (e.g. shift+cmd+←, shift+↑, shift+↑, shift+cmd+L). The last one is the Apple Notes shortcut for creating checklists.

Just an observation: The Menu Bar Search workflow can't find the "Tags..." item either. It looks like you've run into an inconsistency with this particular menu item. Both the Automation Task and the Menu Bar Search workflow failing to interact with it suggests this simply might be an outlier in its behaviour. Aaand some probing seems to confirm it. Apparently the item doesn't even exist 🥲 on run argv tell application "System Events" set finderProcess to a reference to (first application process whose name is "Finder") set fileMenuBar to (a reference to menu 1 of menu bar item "File" of menu bar 1 of finderProcess) --set tagsMenuItem to (first menu item of fileMenuBar whose name begins with "Tags") -- no match set allMenuItems to menu items of fileMenuBar --set probablyTagsMenuItem to item 39 of allMenuItems -- Should be "Tags..." but fails --click probablyTagsMenuItem -- no effect --return set allMenuItemsCount to count of allMenuItems repeat with i from 1 to allMenuItemsCount set menuItem to item i of allMenuItems -- Get the menu item at index i set theName to name of menuItem as text display dialog theName & " - Number: " & (i as text) end repeat end tell end run

I want to call attention to some aspects that are easily overlooked and share some tips. Note the hidden options, i.e. modifiers mentioned in the documentation to make use of Multi-Line prompt editing Vocalization of the most recent answer (See here how to change the voice) The HUD to quickly check your most important current settings. Some third party proxies allow you to use certain models for free. For example, Groq currently grants access to Llama 3 70B, which is en par with Gemini 1.5 Pro according to some benchmarks. OpenRouter curates a list of free models that can be used with their API. The new API for Google's Gemini is currently in beta. If your API requests are detected as coming from the US, Gemini comes with a substantial free tier quota for both Gemini 1.5 Flash and Pro. I also encourage you to explore local LLMs. Meta recently released their Llama 3 model, and the "tiny" Llama 3 8B performs beautifully on newer Macs. According to some benchmarks, the 8B version competes with GPT 3.5 Turbo, and I can confirm that I was at least very positively surprised by its capabilities. Related: Ollama Workflow.

Hey everyone! I'm excited to share the alpha preview of Ayai - GPT Nexus with you, a workflow that lets you interact with various AI language models. The workflow integrates APIs from OpenAI, Anthropic, and Google, while also supporting local LLMs. Why an Alpha Preview? While Ayai - GPT Nexus is still a work in progress, it’s already quite useful. Development has slowed down recently, and I’m not actively working on it as much. Rather than keep it under wraps until it's perfect, I wanted to release it now so you can take advantage of its current features and provide feedback that could shape its future development. Current Features Chat with AI Models: Interact with ChatGPT, Claude, Perplexity, and Gemini. Third-Party Proxies: Connect through OpenRouter, Groq, Fireworks, Together.ai, and other proxies compatible with OpenAI's response format. Local LLMs: Use local models via interfaces like Ollama or LM Studio. Live Web Search: Enable live web search for OpenAI models with additional Exa.ai or Azure API keys (experimental). What’s Missing? The "Ayai" part of the name hints at some personal AI assistant features I have in mind and plan to explore in the future. Additionally, the text processing features like paraphrasing, simplifying, changing the tone of text, or summarizing documents (PDFs, docx, text files, etc.) without needing to go through the chat window are still on the to-do list. Your feedback is, of course, appreciated! Download here: Ayai · GPT Nexus on Github Looking forward to hearing what you think!

Window Navigator v1.2.0 I successfully rewrote the program to rely solely on the Accessibility API 🎉 By removing all AppleScript components, the program is now more predictable, reliable, and faster.

Curious. You can try the updated version now to see if the problem is fixed! FYI, if you want the workflow to be more responsive, you can install the Xcode Command Line Tools to create and use a compiled version. xcode-select --install

Added a third option to navigate all visible windows of all apps globally over all desktop spaces

What I was missing in the existing window switchers was a way to navigate between windows of the same application that are scattered across different desktop spaces, so I created one that does just that 😄 Window Navigator Navigate to any window of the currently focused application or any application across all desktops, or switch windows within the current desktop space. Usage Search the windows of the active app globally using the Navigator keyword. Search app windows in the current desktop space using the Switcher keyword. Search all visible windows of all apps globally using the Global keyword. ⏎ to navigate to the selected window. ⌘⏎ to close the selected window. ⌥⏎ to quit the owning application. Configure the hotkeys for quick access. 1. Navigator 2. Switcher 3. Global