How to get notified when Codex finishes a task

With SpeakApp, Codex's reply is read aloud as soon as it is ready, after your other agents' replies. You say “ok”, answer, say “enter”, and your message goes into the right session. Codex also has its own notification settings, which this page summarises from its documentation. A ready reply is not a successful task: read the result before you accept it.

How do you get notified with SpeakApp?

SpeakApp reads replies from the Codex Windows app. As soon as Codex finishes answering, its reply joins the queue and is read aloud, in turn with your other agents' replies.

  1. Start your task in Codex and move on: a meeting, an email to a client, another session.
  2. The reply arrives: the toast, a card at the top right of your screen, offers read, skip, later, reply and open. The widget's circle counts what is waiting.
  3. Listen to what Codex says it did, then say “ok” to answer that conversation.
  4. Dictate your answer and say “enter”: it is pasted and sent into the Codex session that spoke.

A sound only tells you something happened. Hearing the reply gives you the agent's explanation before you decide whether to go back to its window.

What does Codex offer on its own?

According to Codex's documentation, there are two settings, in its config.toml file.

  • notify runs a program of your choice when Codex emits an event. Currently there is one: agent-turn-complete, the end of a turn. The program receives a JSON argument (event type, thread id, working directory and the last assistant message).
  • tui.notifications, for Codex's terminal interface, turns built-in notifications on or restricts them, for example to the end of a turn or an approval request. tui.notification_method picks the method (auto, osc9 or bel) and tui.notification_condition says whether they fire only when the terminal is unfocused or always.
notify = ["python3", "/path/to/notify.py"]

Adapt the path and interpreter to your machine. These settings give you an alert. Reading aloud and answering in the session are what SpeakApp adds.

When several agents reply at once

One Codex session investigates a failing test, another reviews a proposal, a ChatGPT conversation in Chrome helps you draft an explanation. The replies wait in the queue and are read one after another. You say “ok” for the one on screen, “skip” for the next, “later” to keep it. One way to organise your work among others.

Keep reading

SpeakApp is available on Windows, coming soon to Mac. See pricing for the free plan.

Frequently asked questions

How can I hear when Codex has a reply ready?

With SpeakApp, the reply from the Codex Windows app is read aloud as soon as it is ready, in your agents' queue. The toast offers read, skip, later, reply and open.

Can I reply to Codex by voice?

Yes. Say “ok” to answer the conversation in the toast, dictate your answer, then say “enter”: it goes into the Codex session that spoke.

Does Codex have its own notifications?

Yes, according to its documentation: the notify setting runs a program at the end of a turn, and tui.notifications handles notifications in its terminal interface.

What happens when several conversations have replies waiting?

They wait in a queue and are read one after another. The widget's circle counts what is still waiting.

Does a ready reply mean the task succeeded?

No. A reply can report a change, ask a question or flag a problem. Check the result before you accept it.

Try SpeakApp

SpeakApp is available on Windows, coming soon to Mac. Download SpeakApp or join the Mac waiting list. To see the whole product first: What is SpeakApp?