Notification bell not working as it should be

[Thanatermesis]

Issue

This doesn't seems to be correct:

  --notifications, --no-notifications
                        Enable/disable terminal bell notifications when LLM
                        responses are ready (default: False) [env var:
                        CECLI_NOTIFICATIONS]
  --notifications-command COMMAND
                        Specify a command to run for notifications instead of
                        the terminal bell. If not specified, a default command
                        for your OS may be used. [env var:
                        CECLI_NOTIFICATIONS_COMMAND]

Actually I don't receive a notification bell, which can be emulated with this command:

sleep 5 ; echo -e "\a"

note: in some desktops, unfocus the terminal window before 5 seconds in order to see the bell better

Instead, it shows me GUI notifications, not very useful since it annoys my visiliby all the time and also the bell can trigger a blink in my pager so I can see exactly "where is required attention"

How I can configure it to use the real bell instead of GUI ballon notifications ?

Maybe we would want to have two options, one for GUI notifications and one for Bell notifications ?

Version and model info

No response

[dwash96]

Ah got it, we are suppressing the notification command outputs as we are running them detached/in-the-background. I'll add in v0.100.11 an update where, if the command contains some combination of "print|echo" and "\a" anywhere in its body it will enable the output to trigger terminal bells. Should prevent configuration sprawl

[Thanatermesis]

I will be impatient for that :)

on the other side, im not sure how to implement that, so basically my shell has a lot of aliases with predefined settings, adding quotes and single quotes is a bit conflicting, also escaping the escape

Thats why I was suggesting to use different settings of notifications, one for gui notifications and one for terminal (bell) notifications, in this way is more easy to set up and compatible, and the users can have also both of them (which can be good in many situations like important ones running cecli)

maybe --notification-bell or --bell , just like --no-bell or --no-notification-bell

[dwash96]

Gotcha, I added a pre-release v0.100.11rc1 with the behavior in the way I described in my last message but I see what you're saying about an additional argument now since you're using custom aliases/scripts.

I think the only thing I'm trying to prevent is having to maintain two different sets of semantics on "when to pop a gui notification" vs. "when to trigger an audio bell" since notifications are fairly sprawling. I'll add a --notification-bell argument that's on by default since it does make sense to me to pop whatever is provided in the notification command however its specified

[dwash96]

Alright, preliminarily in v0.100.11rc2 let me know if this does what you'd expect

[Thanatermesis]

Installed up to the .10 version:

~ ❯❯❯ pipx upgrade cecli-dev
upgraded package cecli-dev from 0.100.8 to 0.100.10

[dwash96]

For pre release versions with pipx the command appears to be pipx install cecli-dev --pip-args="--pre". I use uv where I can also specify the package version explicitly as cecli-dev==0.100.11rc2 which may be common across all python package managers but I am not 100% sure on that

[Thanatermesis]

just tried, i have "--notifications --notification-bell", moved to another desktop, and I got my "notification ballon" in the corner but seems like teh terminal bell has not been triggered