%FrontBrowserURL% token fails on macOS 26 (Tahoe) – AppleScript works

Questions & Suggestions
,
1

Hi Peter,

I'm running into an issue with the %FrontBrowserURL% token (and presumably related front-browser tokens) on macOS 26.4 and 26.4.1 (did not try before on older releases):

Setup:

  • macOS 26.4.1, MacBook Pro M5

  • Keyboard Maestro 11.0.4

  • Safari (also tested with Chrome Canary)

Symptom: When a macro uses %FrontBrowserURL%, I get the following error notification:

Set Variable to Front Browser Field failed to get value of field %FrontBrowserURL% in macro "…" (while executing Set Variable "local_URL" to Front Browser Field "%FrontBrowserURL%")

What I've already tried (no effect):

  • Safari → Developer Settings → "Allow remote automation" and "Allow JavaScript from Apple Events" are both enabled

  • Keyboard Maestro has Safari automation permission in System Settings → Privacy & Security → Automation

  • sudo tccutil reset AppleEvents + restart of Keyboard Maestro Engine

  • Reinstalled Keyboard Maestro over the existing install

  • codesign --verify passes for both the app itself and the Engine

  • Error occurred first on 26.4, later updated macOS to 26.4.1

What works: An Execute AppleScript action with:

tell application "Safari"
    return URL of front document
end tell

returns the URL reliably. So AppleScript access to Safari itself is fine — the issue seems to be specific to how the %FrontBrowserURL% token resolves internally on macOS 26.

Notably, KM Engine never appears in the Automation permissions list in System Settings, only "Keyboard Maestro" itself does. No permission prompt for the Engine ever triggers, even after a full TCC reset.

Happy to provide more diagnostics if useful.

Thanks for KM — it's an indispensable tool.

Best, Martin

2

It works fine here on the same OS. What appears in the Accessibility section of Privacy & Security? Both the engine and the app need to be there.

-rob.

3

Thanks for your quick response!

In “Accessibility”, there are both, KM and the engine. In “Automation”, just KM, not the engine.

Weird is, that the macro works accessing Safari using AppleScript, that should be the same security context as far as I understand?

4

Automation is fine, at least it matches my setup. No idea why it's not working for you. You might try an Accessibility reset, though those are a royal PitA to set up everything again.

-rob.

5

Have you checked the Security preferences in Keyboard Maestro, it can run a test of controlling a web browser.

Does the %SafariURL% token work?

Do other web browser tokens/actions work?

6

@peternlewis

%SafariURL% is also not working. %ChromeURL% also not (might be a Chrome Canary thing, though).

The test works for Safari, not for Chrome (Canary).

image
image1078×714 100 KB

Chrome Canary is not important for my daily life, I use Safari most of the time. Just tested it with another browser.