Trying to use Terminal for Display Notification

AppleScript
#1

Hi all !
In macOS Sequoia, if I run in SD:
display notification "Hi all"
it works as expected.

But if I use in Terminal:
osascript -e 'display notification "Hello from me" with title "Hello"'
is not working!!

But “display dialog” works perfectly:
osascript -e 'display dialog "Hello from me" with title "Hello"'

I don’t understand why display notification cannot be triggered from Terminal anymore…
Any Help ?
Thanks

Luciano

1 Like
#2

Works for me.
Have you activated the focus mode? I had to add the Script editor to the allowed apps to make the notification visible.

#3

This is the answer. If I have Focus turned on, the notification doesn’t appear. If I have Focus turned off, it appears.

#4

Unfortunately is not matter of ‘Focus’ since: 1) is not active; and 2) I do get notifications if I invoke Display Notifications from the Script Debugger. But I do not get any notification when I run the same command from Terminal.
Any other idea?

#5

Then execute the command again in the Script Editor (not Script Debugger) and see if the notification is displayed. If not, then check the notification setting of the Script Editor. It seems that osascript is running in its context and there are separate settings for notifications for each app.

Otherwise you could try the following again:

osascript <<EOF
	display notification "Hello from me" with title "Hello"
	delay .5
EOF
1 Like
#6

I did run in Script Editor (and not in SD):
display notification "Hi all"

It actually asked me to allow Notifications for Script Editor!
And – as expected – I got the notification.

I then run in the Terminal (as Dirk suggested):
osascript <<EOF
display notification “Hello from me” with title “Hello”
delay .5
EOF

and it also worked!!!

Finally I run the code that initially for me was not working:
osascript -e 'display notification "Hello from me" with title "Hello"'

But NOW it worked!!!

Thanks a lot Dirk !!!

1 Like
#7

Hey guys, just stopped by to say thank you.

I was searching all over the internet trying to figure out why the osascript command wasn’t working. I had it embedded in a Python script that I was running via launchd on my MacBook to automate a task and trigger a notification every minute.

And this solution worked perfectly, i needed to run an osascript command in the script editor once to grant permission. This is a really silly mistake from apple if you ask me, the system should prompt for permission when you are trying to run it from the terminal. But well, im still new to programming so i dont know lol.

If you ever organize group work sessions over other channels (discord, etc) please let me know, I’m looking to join a team to collaborate and share what I’ve been learning.

#8

Hi,

I did have this working, but now it quit working. I haven’t used osascript for a few years and now I’m trying to use it in a small project. I followed the above and gone through several things to get it to work. But, I still can’t get notifications, just dialogs.

MacOS 26.3 (25D125) on a MacBook Pro M1 chipset.

Anyone know why?

#9

Permissions must always be granted to the process that ultimately executes the script. If osascript is run in Terminal, then Terminal must have permission to display notifications or run automations. If it is called from Script Editor, then it is Script Editor, and so on.

Also check whether a focus is preventing or filtering the display of notifications.

If the calling app is not signed or notarised (see SD Notary), the system may ignore the settings for displaying notifications.