14.4.2-beta.5

Features

• notifai doctor codex helps you approve Notifai's Codex hooks. Run it in a terminal: it finds the Codex homes where they still wait, such as a T3 Code account's own home, and opens Codex's own hook review in each one, with no sign-in. You approve there and it checks the result. Notifai never approves its hooks itself, and when an agent runs the command it only says what you should run.

Bug Fixes

• A Codex session keeps the Notifai hooks it loaded when it started. After an update adds or changes one, notifai update --resume no longer says the update is done for that session: it names the hooks the session is missing and says a new Codex session picks them up. notifai doctor names them too, and only treats it as a problem when a feature needs one (answers at turn end, Notes during a busy turn, question cards).
• New Codex installs no longer add an --integration-revision argument to their hook commands. Existing installs keep their commands exactly as they are, so nothing needs approving again. notifai doctor asks Codex itself whether the hooks are approved when it can.
• A Codex thread whose Notifai hooks Codex skips, such as one started with its own CODEX_HOME for another account, now shows as running in the Notifai apps once it sends. Until its hooks are approved in that home it takes no notes and can't ask questions.
• The agent in such a thread is told once to remind you to approve the hooks, with the step that works there. In apps that run Codex for you, such as T3 Code and Orca, that is notifai doctor codex in a terminal, the same on every platform. In Orca one approval in ~/.codex covers every account. notifai init and its done message give the same step.
• With a symlinked ~/.codex, hooks you approved are no longer reported as waiting for approval.

14.4.2-beta.4

Bug Fixes

• A Codex session keeps the Notifai hooks it loaded when it started. After an update adds or changes one, notifai update --resume no longer says the update is done for that session: it names the hooks the session is missing and says a new Codex session picks them up. notifai doctor names them too, and only treats it as a problem when a feature needs one (answers at turn end, Notes during a busy turn, question cards).
• New Codex installs no longer add an --integration-revision argument to their hook commands. Existing installs keep their commands exactly as they are, so nothing needs approving again. notifai doctor asks Codex itself whether the hooks are approved when it can.
• A Codex thread whose Notifai hooks Codex skips, such as one started with its own CODEX_HOME for another account, now shows as running in the Notifai apps once it sends. Until its hooks are approved in that home it takes no notes and can't ask questions.
• The agent in such a thread is told once to remind you to approve the hooks, with the step that works there. In apps that run Codex for you, such as T3 Code and Orca, that is a terminal command that opens Codex's hook review with no sign-in: CODEX_HOME=<home> codex -c model_provider=ollama, then Trust all and continue. On Windows the command clears CODEX_HOME afterwards, and in Orca one approval in ~/.codex covers every account. notifai init and its done message give the same step.
• With a symlinked ~/.codex, hooks you approved are no longer reported as waiting for approval.

14.4.2-beta.2

Bug Fixes

• A Codex thread whose Notifai hooks Codex skips, such as one started with its own CODEX_HOME for another account, now shows as running in the Notifai apps once it sends. Until its hooks are approved in that home it takes no notes and can't ask questions.
• The agent in such a thread is told once to remind you to approve the hooks, with the step that works there. In apps that run Codex for you, such as T3 Code and Orca, that is a terminal command that opens Codex's hook review with no sign-in: CODEX_HOME=<home> codex -c model_provider=ollama, then Trust all and continue. On Windows the command clears CODEX_HOME afterwards, and in Orca one approval in ~/.codex covers every account. notifai init and its done message give the same step.
• With a symlinked ~/.codex, hooks you approved are no longer reported as waiting for approval.

Notifai for Mac 0.1.5

Notifai 0.1.5 for Mac.

Notifai for Mac 0.1.4

Notifai 0.1.4 for Mac.

14.4.2-beta.1

Bug Fixes

• A Codex thread whose Notifai hooks Codex skips, such as one started with its own CODEX_HOME for another account, now shows as running in the Notifai apps once it sends. Until its hooks are approved in that home it takes no notes and can't ask questions.
• The agent in such a thread is told once to remind you to approve the hooks, and the reminder names the step that works for that home: run CODEX_HOME=<home> codex in a terminal, then type /hooks.

14.4.1

Bug Fixes

• The hub keeps attending sessions when a local write fails, for example on a full disk. Its exchange loop retries instead of stopping, a watchdog restarts a loop that stalls, and a Stop hook hands an answer back itself when the hub holding its question has stopped moving.
• The local log survives a full disk: it pauses briefly after a failed write instead of going quiet for the rest of the process, and it no longer leaves a broken record behind.

14.4.1-beta.1

Bug Fixes

• The hub keeps attending sessions when a local write fails, for example on a full disk. Its exchange loop retries instead of stopping, a watchdog restarts a loop that stalls, and a Stop hook hands an answer back itself when the hub holding its question has stopped moving.
• The local log survives a full disk: it pauses briefly after a failed write instead of going quiet for the rest of the process, and it no longer leaves a broken record behind.

14.4.0

Features

• Setup messages put one idea per paragraph: the approval code on its own line, named links and numbered phone steps, so the code and link are easy to spot.
• On macOS, setup no longer suggests the Mac app when it is already installed.
• Codex hook approval is worded for the Codex you use: /hooks in the Codex CLI, or the Review hooks icon by the message box in the ChatGPT desktop app and the Codex IDE extension, and both when Notifai can't tell. Outside setup, agents no longer wait for that approval; they carry on and end their reply with a short reminder.

Bug Fixes

• The hub no longer resends an attendance exchange the service refused. A conversation that resumed after its end was recorded could keep a hub retrying about once a second.
• Responses from the Notifai service (registration, media uploads, access, changes and retained feed content) are checked before they are used.

14.4.0-beta.1

Features

• Setup messages put one idea per paragraph: the approval code on its own line, named links and numbered phone steps, so the code and link are easy to spot.
• On macOS, setup no longer suggests the Mac app when it is already installed.
• Codex hook approval is worded for the Codex you use: /hooks in the Codex CLI, or the Review hooks icon by the message box in the ChatGPT desktop app and the Codex IDE extension, and both when Notifai can't tell. Outside setup, agents no longer wait for that approval; they carry on and end their reply with a short reminder.

Bug Fixes

• The hub no longer resends an attendance exchange the service refused. A conversation that resumed after its end was recorded could keep a hub retrying about once a second.
• Responses from the Notifai service (registration, media uploads, access, changes and retained feed content) are checked before they are used.