I have one macro that is creating 2-3 lines in Engine.log for every single MIDI note I play — hundreds or thousands per day — and it feels a bit weird and messy. Is there a way to make this particular macro not record anything in the log?

Peter has addressed this in the past, and I would imagine it's still off the table. Going off of Peter's suggestion in the post linked above, this macro provides a running display of the log file with "My Frequent Macro" excluded. Tail Engine.log with exclusion.kmmacros (3.6 KB) ▶ Macro image

[image] nrightnour: Is there a way to make this particular macro not record anything in the log? Nope. If a macro is triggered, it is recorded in the log file. This is probably the most important thing for the log file to record.

Additionally, you could run a script to reset the log, possibly with a Time of Day trigger every night: cd /Users/$USER/Library/Logs/Keyboard\ Maestro/ cp Engine.log "$(date +%Y%m%d)-Engine.log" && truncate -s 0 Engine.log This may come with drawbacks that I'm not aware of, so we might need @peter…

Keyboard Maestro rolls the log itself. Any time the Engine or Editor launch the log file will be trimmed down to 7MB if it is over 13MB, so if you really want to roll the log, all you need to do is re-launch the Engine or the Editor.

[image] nrightnour: Is there a way to make this particular macro not record anything in the log? Hi, @nrightnour . As @peternlewis stated, there's no way to prevent the Engine.log entries, but I've recently shared a macro that can be used to remove such entries: Engine.log Tool

This is impressive! A bit bigger scope than I was thinking, but a nice option to have. Thanks :slight_smile:

[image] peternlewis: This is probably the most important thing for the log file to record. But what is so important about this that it must be enabled even if I don't need this noise on every key press and would like to disable it just like other users reporting about this issue?

[image] esv: But what is so important about this that it must be enabled even if I don't need this noise on every key press and would like to disable it just like other users reporting about this issue? The primary purpose of the log is to record macros fired so that if anything on your Mac i…

[image] peternlewis: so that if anything on your Mac is behaving oddly you can look in the log and verify whether macros are being fired as a possible cause. And it has served this purpose for my debugging purposes exactly 0 times, that flood is useless, even when I wanted to test the working…

[image] peternlewis: grep -v 'Execute macro “Update” from trigger' Engine.log | tail Just to expand on that useful tip a little: Engine.log is a placeholder for the full path to the log. The path should be wrapped in typewriter ("dumb") quotation marks (either double or single). Here is an e…

Prevent a macro from writing in Engine.log

Questions & Suggestions

_jims September 8, 2026, 12:50pm 12

Hi, @nrightnour. As you’ve already heard, no there isn’t. But the following macro can be used to remove such records. If you want to routinely remove the records you could run the reduction step on a schedule.

Prevent a macro from writing in Engine.log

Options