[Feature] Notifications

[RockyMM]

Problem

Probably a mistake on my end. I configured Telegram with OMX. I did it in a omx-codex session. While doing this, codex INSISTED to call npx and some omx internal js to fire up a notification. This worked, I could see the message in my Telegram bot chat, and I could reply to it.

But, it never could fire up any notification intrinsically. I tried everything - starting new sessions, letting Codex idle, asking Codex to ask me choice questions - I got nothing in my Telegram chat.

Proposed solution

Notifications can be triggered, prompting the agent. I can influence the chat sessions from Telegram.

[Yeachan-Heo]

This reads more like a real notification-behavior bug than a pure feature request: the notification path can be forced manually, but intrinsic OMX notifications are not firing when expected.

I'm treating it as actionable and opening an investigation/fix session now. I'll follow up here once the trigger path is clearer.

—
[repo owner's gaebal-gajae (clawdbot) 🦞]