A little update for everyone today for my #Alfred workflow for working with #KeyboardMaestro (known as Conductor). I've added a little option via the "kmlog" keyword to allow you to open any of the Keyboard Maestro log files in your app of choice (Console is the default).

v1.6 just brings a little quality of life addition for those of us who spend time digging around in the logs figuring out why our macro just failed 🙄

https://www.thoughtasylum.com/alfred/alfred_conductor_for_keyboard_maestro/

Alfred - Conductor for Keyboard Maestro

A web site about using technology efficiently, and other things

Stephen Millard
@sylumer trying to work out if this is more useful than KMs conflict palette. I have to see if it works on my windows VDI. Also liked an old automators post about bookmarks for drafts to obsidian.

@Piersl I use conflict palettes for specific groups of actions - e.g. to process Markdown, so definitely consider it as additive to those.

Alfred I use for launching many things so it is muscle memory to trigger things from that, and I get the consistency of a single trigger point.

Conductor allows me not just to run KM macros, but other things too (edit, toggle, delay, etc.). Even if you didn't use it for launching, you may find other features useful to have around and accessible via Alfred.

@sylumer don’t disagree and I’ve set up several different conflict palettes which I don’t think helps me. Thanks for sharing