NM call to the AHK script
Just keep in mind that any parameters you want to pass from the extension to the native script/program/app/… are sent and replied to via the native messaging protocol over stdio. I don’t think it is fun to implement or debug that with AHK scripts, if it is possible at all.
To store the “profile<->icon path” relation in the AHK, I’ll have to pass the profile name too to the script, I guess that’s possible ? When launching a profile via the integrated way, the session name is not in the program command line.
See above. That alternative would be an individual script with distinct name per profile. The extension could call the script belonging to the profile without any parameters.
And getting the current profile isn’t straight forward either:
Or you could use my “node brick” as a proxy that takes care of the messaging and figuring out where the current profile is located, so you could simply call your scripts with parameters or use ffi 