Add notify trigger when user permission is required during conversation

Resolved 💬 2 comments Opened Nov 7, 2025 by BobbyWang0120 Closed Nov 7, 2025
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What feature would you like to see?

Feature Request: Notify Trigger for Permission Requests during Conversation

Currently, the notify mechanism only runs after a conversation finishes, executing the user-defined notification script once the task is complete. However, during a session, Codex may pause and require the user to grant permission to execute certain actions, such as running a bash command. Users are often unaware that Codex is waiting for their input because no notification is triggered until the end of the conversation.

Proposed Enhancement:

  • Implement a notification trigger that runs the user's notification script whenever Codex pauses to request permission from the user during an ongoing conversation, not just at the end.
  • This trigger would alert users through their preferred notification channel (as defined in their script) that their input is required, ensuring they know to return to the conversation promptly.

Rationale:

  • Users may step away during long-running tasks and not realize that Codex is awaiting their permission, leading to delays.
  • A mid-conversation notify mechanism would improve the user experience by reducing idle time and helping tasks progress smoothly.

Thank you for considering this feature.

Additional information

_No response_

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 9 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #6024
  • #4349

Powered by Codex Action

etraut-openai contributor · 9 months ago

Thanks for the suggestion. This feature is being tracked by this enhancement request. Please upvote that issue. If it doesn't fully capture what you're looking for, feel free to add more details.

I'm going to close this one to avoid duplication.