AI

Notifications and session activity

Choose completion notifications and inspect or stop ongoing Codex sessions.

Start with Open Codex chat if you have not used the agent before.

Get a notification when a turn finishes

In account settings, find Notifications and Codex and agents. Notify when Codex turns complete by default sets the preference for threads that inherit the account default. The channel table separately controls Inbox, Toast, Browser, and Email for Needs attention, Turn completed, and Turn failed.

To set a thread's completion preference:

  1. Open its menu and choose Behavior....
  2. In Edit Thread Behavior, clear Mute completion notifications for this thread to request notices, or check it to mute them.
  3. Confirm the dialog. Changing this checkbox saves an explicit preference for that thread.

Set the preference before starting work when possible. A turn's completion can race with a settings change, and changing settings does not withdraw a notice already produced.

Delivery depends on the enabled channels and site settings. CoCalc can show a toast while its page is visible or a browser notification while it is hidden. Browser delivery also needs browser permission; use Enable browser notifications and Test notification in account settings. CoCalc suppresses the extra toast or browser alert when you are directly watching that thread.

In CoCalc, successful completion uses Codex turn finished; an error uses Codex turn ended with an error. Browser notifications use the generic title Codex finished; open CoCalc to inspect the outcome. A completion notice does not establish that every background command or descendant agent has stopped. Inspect the account's Codex sessions panel when you need to confirm remaining activity.

Inspect and stop Codex sessions

Open account AI settings and choose View Codex sessions. The panel groups recent turn records by session. Active or unconfirmed turns take precedence over completed turns in the status column; model, payment source, and update time come from the latest turn. Use Open chat, when available, to return to its chat file. Some records omit details you cannot access.

The list and account stop request operate on a bounded set of recent records, not an exhaustive inventory or an instant guarantee that all account activity has ended. Refresh and inspect the reported outcome after requesting a stop.

  1. Click Refresh to update the list.
  2. Use a row's Stop all control to request interruption of that session, or Stop all active or uncertain for the account-level stop action.
  3. Read the result and refresh again if interruption could not be confirmed.

An uncertain state, stale heartbeat, or failed interrupt can mean CoCalc cannot yet establish whether AI activity has ended. The panel keeps those records visible as possible ongoing resource use. It can also report active descendant threads or background commands, with a warning that usage may continue.

Treat an interruption request as pending until the status confirms its outcome. A finished manager response alone does not establish that all of its reported descendant work has ended.