Release history

Changelog

· Beta release

Notifai update

  • CLI 14.7.6-beta.1 · native CLI · npm launcher

What changed

  • Claude Code agents can ask questions again in profiles that still had an old Notifai worker hook. Notifai removes that hook from the profile in use and keeps your other hooks.
  • Claude Code workers waiting on your answer are no longer held at their stop and made to repeat their report. Your answer reaches the parent session, with the worker and the work it unblocks.
  • In Grok, a reply with no tool calls now just ends. Notifai's guidance arrives with the first tool result instead of forcing a second turn.
  • Notifai now works with Hermes v0.21.5 through v0.23.3. When Hermes runs a turn in its gateway, `notifai ask --wait` returns your answer to that command; in the classic CLI, your answer can reach the session after the command ends.
  • `notifai doctor` now tells you whether the installed OpenCode plugin fits your version, and asks you to confirm it is active with a new prompt. An OpenCode 2.3 policy can still block it, and reinstalling it does not change that.
Full CLI changelog for 14.7.6-beta.1

Bug Fixes

  • Claude Code agents can ask questions again in profiles that still have an old Notifai worker hook. Notifai cleans up that hook in the profile the agent is using and preserves other hooks.
  • The Hermes plugin supports stable releases from v0.21.5 through v0.23.3. When the gateway owns the turn, notifai ask --wait returns the answer in that command. When the classic CLI owns the turn, an answer can return to the session after the command exits.
  • OpenCode doctor reports whether the installed plugin matches the OpenCode version. A match is compatibility, not activation. OpenCode 2.3 can block a compatible plugin by policy, and installing the plugin again does not change that policy.
  • Claude Code workers can report a waiting question and return to their parent in one turn. The parent receives the answer with the worker’s identity and the work it resumes.
  • Grok can finish a tool-free turn immediately. Notifai adds guidance to the first tool result, including after resume or compaction.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI · npm launcher

CLI 14.7.5-beta.3

What changed

  • Notifai now works with Hermes v0.21.5 through v0.23.3. When Hermes runs a turn in its gateway, `notifai ask --wait` returns your answer to that command; in the classic CLI, your answer can reach the session after the command ends.
  • `notifai doctor` now tells you whether the installed OpenCode plugin fits your version, and asks you to confirm it is active with a new prompt. An OpenCode 2.3 policy can still block it, and reinstalling it does not change that.
Generated changes since 14.7.5-beta.2

Sources for the summary

  1. Note 1: commit 2c8cb5f
  2. Note 2: commit 51378eb

Bug Fixes

  • The Hermes plugin supports stable releases from v0.21.5 through v0.23.3. When the gateway owns the turn, notifai ask --wait returns the answer in that command. When the classic CLI owns the turn, an answer can return to the session after the command exits.
  • OpenCode doctor reports whether the installed plugin matches the OpenCode version. A match is compatibility, not activation. OpenCode 2.3 can block a compatible plugin by policy, and installing the plugin again does not change that policy.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

Earlier betas for 14.7.5 (2)

· Native CLI · npm launcher

CLI 14.7.5-beta.2

What changed

  • A Claude Code worker can report a question it is waiting on and return to its parent once. When you answer, the parent receives your answer with the worker’s identity and the work it unlocks.
  • Grok can finish a turn without calling a tool. Notifai adds its guidance to the first tool result, so a simple reply no longer triggers a second turn asking the agent to load guidance.
Generated changes since 14.7.5-beta.1

Sources for the summary

  1. Note 1: commit d459d22
  2. Note 2: commit b1d7cee

Bug Fixes

  • Claude Code workers can report a waiting question and return to their parent in one turn. The parent receives the answer with the worker’s identity and the work it resumes.
  • Grok can finish a tool-free turn immediately. Notifai adds guidance to the first tool result, including after resume or compaction.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI · npm launcher

CLI 14.7.5-beta.1

What changed

  • Grok can finish a turn without calling a tool. Notifai adds its guidance to the first tool result, so a simple reply no longer triggers a second turn asking the agent to load guidance.
Full generated changelog

Sources for the summary

  1. Note 1: commit b1d7cee

Bug Fixes

  • Grok can finish a turn without calling a tool. Notifai adds its guidance to the first tool result, so a simple reply no longer triggers a second turn asking the agent to load guidance.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Beta release

Notifai update

  • Mac 0.1.11-beta.2 · direct download
  • Windows 0.1.11-beta.2 · direct download

What changed

  • Sessions in the Edge's peek now highlight as your pointer moves over them, the same as in the open panel.

Get the Mac beta: In Notifai, open Settings, then Updates, and choose Beta.

Get the Windows beta: In Notifai, open Settings, then Updates, and choose Beta.

· Native CLI · npm launcher

CLI 14.7.4-beta.4

What changed

  • In Claude Code, a session that held or missed an earlier Notifai wake no longer leaves your later answers and notes waiting until you type in it. Once the session has gone idle after a turn, Notifai wakes it again and your input reaches the agent; you no longer get a "Not delivered yet" notice for it.
Generated changes since 14.7.4-beta.2

Sources for the summary

  1. Note 1: commit 342ded8

Bug Fixes

  • In Claude Code, a session that held or missed an earlier Notifai wake no longer leaves your later answers and notes waiting until you type in it. Once the session has gone idle after a turn, Notifai wakes it again and your input reaches the agent; you no longer get a "Not delivered yet" notice for it.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

Earlier betas for 14.7.4 (1)

· Native CLI · npm launcher

CLI 14.7.4-beta.2

What changed

  • In an Orca chat, an answer you give on your phone to one of a Codex agent's question cards now reaches the agent at once, even while another of its cards is still unanswered. Orca's chat stops showing that other card, as it does when you answer one card there, but its question stays open on your devices and the agent is told so; your later answer to it still reaches the agent.
Full generated changelog

Sources for the summary

  1. Note 1: commit 6fda73a

Bug Fixes

  • In an Orca chat, an answer you give on your phone to one of a Codex agent's question cards now reaches the agent at once, even while another of its cards is still unanswered. Orca's chat stops showing that other card, as it does when you answer one card there, but its question stays open on your devices and the agent is told so; your later answer to it still reaches the agent.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI · npm launcher

CLI 14.7.3-beta.2

What changed

  • Agents ask each question one way, so your devices show one question instead of a reworded copy. In Codex, the agent's own question card can now be that same question.
  • When you answer a Claude Code agent in its chat, it sees which of its questions are still waiting on your devices and can close the one you answered. Closing one question no longer closes the agent's other open questions.
Generated changes since 14.7.3-beta.1

Sources for the summary

  1. Note 1: commit b1c919c · commit 2e6749f
  2. Note 2: commit b1c919c · commit 0c3a7eb · commit 695f65d

Bug Fixes

  • Agents are told to ask each question one way: through a question form Notifai links, or with notifai ask, not both. When Notifai hands back a question form for a registered question, the agent opens it with the exact wording, so it stays the same question on your devices instead of becoming a second, reworded one.
  • In Codex, notifai ask can now hand back the first question as an exact card to open when the card tool is available, so that card is the same registered question.
  • When a User types a new message to a Claude Code agent, the agent is shown its questions still open on the User's devices, each with its close command. It is asked to close only the ones the message answers. Nothing is closed automatically.
  • Closing one question no longer ends an agent's other open questions. Each stays answerable for its own answer window.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

Earlier betas for 14.7.3 (1)

· Native CLI · npm launcher

CLI 14.7.3-beta.1

What changed

  • After Claude Code restarts in place, answers and notes from your phone reach the restarted session instead of waiting unseen, and the notice about waiting input names its question and session.
Full generated changelog

Sources for the summary

  1. Note 1: commit c423246

Bug Fixes

  • After Claude Code restarts in place, answers and notes from your phone reach the restarted session instead of waiting unseen, and the notice about waiting input names its question and session.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI · npm launcher

CLI 14.7.2-beta.1

What changed

  • When an agent reads Notifai's guidance in one folder and sends from another, a refusal now names both folders and the one command that fixes it, so the agent is no longer stuck being refused.
  • When the CLI prints anything after a notification went out, the first line now says Sent with its id, so agents no longer mistake advice for a failure and send it twice.
  • Agents are asked to name a Project only when it has no name yet, with a command that works from any folder.
Full generated changelog

Sources for the summary

  1. Note 1: commit ebc2182
  2. Note 2: commit ebc2182
  3. Note 3: commit ebc2182

Bug Fixes

  • When an agent reads Notifai's guidance in one folder and sends from another, a refusal now names both folders and the one command that fixes it, so the agent is no longer stuck being refused.
  • When the CLI prints anything after a notification went out, the first line now says Sent with its id, so agents no longer mistake advice for a failure and send it twice.
  • Agents are asked to name a Project only when it has no name yet, with a command that works from any folder.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI · npm launcher

CLI 14.7.1-beta.1

What changed

  • Agents are no longer woken after their turn with a reminder about their own open question, which arrived looking like a message from another session.
Full generated changelog

Sources for the summary

  1. Note 1: commit ec33464

Bug Fixes

  • Agents are no longer woken after their turn with a reminder about their own open question, which arrived looking like a message from another session.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI · npm launcher

CLI 14.7.0-beta.3

What changed

  • Agents write notifications and questions you can understand and answer from your phone alone, and Hermes agents get the full Notifai guidance again.
  • Notifai guidance is on by default in every Project you haven't disabled and outside Projects, a machine setting can require enabling each Project instead, and `notifai guidance edit` opens a topic in your editor.
  • Agents are reminded when a question they asked is still waiting, so they don't report that work as done; the update adds a Claude Code hook for this, so it waits until you approve it once.
Generated changes since 14.7.0-beta.2

Sources for the summary

  1. Note 1: commit 884dd8b · commit 23bbcb6
  2. Note 2: commit abb2f0e · commit 46cbb62
  3. Note 3: commit 8e52b53 · commit b644e46

Bug Fixes

  • Agents are reminded when a question they asked is still waiting, so they don't report that work as done; the update adds a Claude Code hook for this, so it waits until you approve it once.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

Earlier betas for 14.7.0 (2)

· Native CLI · npm launcher

CLI 14.7.0-beta.2

What changed

  • Agents write notifications and questions you can understand and answer from your phone alone, and Hermes agents get the full Notifai guidance again.
  • Notifai guidance is on by default in every Project you haven't disabled and outside Projects, a machine setting can require enabling each Project instead, and `notifai guidance edit` opens a topic in your editor.
  • Agents are reminded when a question they asked is still waiting, so they don't report that work as done; this adds a Claude Code hook, so the automatic update waits until you approve it once.
Generated changes since 14.7.0-beta.1

Sources for the summary

  1. Note 1: commit 884dd8b · commit 23bbcb6
  2. Note 2: commit abb2f0e · commit 46cbb62
  3. Note 3: commit 8e52b53

Features

  • Agents write notifications and questions you can understand and answer from your phone alone, and Hermes agents get the full Notifai guidance again.
  • Notifai guidance is on by default in every Project you haven't disabled and outside Projects, a machine setting can require enabling each Project instead, and notifai guidance edit opens a topic in your editor.

Bug Fixes

  • Agents are reminded when a question they asked is still waiting, so they don't report that work as done; this adds a Claude Code hook, so the automatic update waits until you approve it once.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI · npm launcher

CLI 14.7.0-beta.1

What changed

  • Agents write notifications and questions you can understand and answer from your phone alone, and Hermes agents get the full Notifai guidance again.
  • Notifai guidance is on by default in every Project you haven't disabled and outside Projects, a machine setting can require enabling each Project instead, and `notifai guidance edit` opens a topic in your editor.
  • Agents can't ask you the same thing twice by opening their own question form right after asking through Notifai, and are reminded when a question they asked is still waiting.
Full generated changelog

Sources for the summary

  1. Note 1: commit 884dd8b · commit 23bbcb6
  2. Note 2: commit abb2f0e · commit 46cbb62
  3. Note 3: commit 556c4e5 · commit 8e52b53

Features

  • Agents write notifications and questions you can understand and answer from your phone alone, never pointing you to the conversation or the terminal.
  • Notifai guidance is on by default in every Project you haven't disabled and outside Projects; a machine setting can require enabling each Project instead.
  • notifai guidance edit opens a guidance topic in your editor.

Bug Fixes

  • An agent can't ask you the same thing twice by opening its own question form right after asking through Notifai.
  • Agents are reminded when a question they asked is still waiting, so they don't report that work as done.
  • Hermes agents receive the full Notifai guidance again.
  • This update adds Notifai hooks in Claude Code, so automatic updates wait until you approve it once, when an agent offers it.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI · npm launcher

CLI 14.6.1-beta.2

What changed

  • Resumed Orca chats receive held answers and notes again, and diagnostics explain when a running chat still needs to reconnect.
  • Prompt-time context stays pending in agent apps whose hooks cannot show it to the model, so it is not silently spent unseen.
Generated changes since 14.6.1-beta.1

Sources for the summary

  1. Note 1: commit 59f9f1a
  2. Note 2: commit 05a0613

Bug Fixes

  • Resumed Orca chats can receive held answers and Session Notes again. Notifai recognizes their direct host independently of changing launch labels, and Doctor explains when attendance has not reconnected.
  • Prompt-time context stays due in agent apps whose prompt hooks cannot show it to the model, instead of being spent unseen.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

Earlier betas for 14.6.1 (1)

· Native CLI · npm launcher

CLI 14.6.1-beta.1

What changed

  • The "Not delivered yet" notification is now corrected when its session ends or the waiting answer expires, instead of asking you to type in a session that no longer exists.
  • A conversation you move to the background right after Notifai starts or updates now keeps its open questions, answers and notes.
  • An agent app started from another one's shell, such as Codex run from Claude Code, now owns its own notifai commands, so its notifications reach the right session.
Full generated changelog

Sources for the summary

  1. Note 1: commit 820f6e0
  2. Note 2: commit 4dc040d
  3. Note 3: commit 9762709

Bug Fixes

  • The "Not delivered yet" notification is now corrected when the session it named ends or the waiting answer expires. Input that went on with a continued conversation takes the notification down; input that never reached the agent replaces it with a plain note that it was dropped, instead of asking you to type in a session that no longer exists.
  • When Notifai has just started or updated, a conversation you move to the background now keeps its open questions, answers and notes. Before, Notifai could decide the move before it knew what the service offers and end the conversation as closed.
  • An agent app started from another agent app's shell, such as Codex run from Claude Code, now owns its own notifai commands. Before, both apps claimed them and sends went out without an Agent Session.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Beta release

Notifai update

  • CLI 14.6.0-beta.1 · native CLI · npm launcher
  • Mac 0.1.11-beta.1 · direct download
  • Windows 0.1.11-beta.1 · direct download

What changed

  • Answers and notes now wake a Codex agent you stopped in the Codex app, Orca or T3 Code without waiting for your next message, and follow a Codex conversation Orca moved to another account; each app has its own wake setting.
  • Codex question cards reach your phone and desktop in every app, and in an Orca chat your answers from a device answer Orca's cards and pausing questions too.
  • A backgrounded Claude Code conversation keeps its questions and notes, setup approves every notifai command at once, and notifai session status shows the name of the session you are in.
  • Notifai for Mac and Windows: the Edge moves more smoothly with less work, images save through your system's Save dialog, and quiet sessions you have read move off Home.
Full CLI changelog for 14.6.0-beta.1

Features

  • Answers and notes now wake a Codex agent you stopped, without waiting for your next message, wherever the app around Codex can start its next turn: the Codex app (including a conversation no window has open, which runs in the background with your hooks intact), an Orca chat, an Orca terminal (typed only into an empty composer, never over a draft) and T3 Code. Each app has its own on/off setting: wake.orca_terminal, wake.codex_app_background and wake.t3, all on by default.
  • In an Orca chat, answering all of a Codex turn's question cards on your phone or desktop now answers them in Orca too, and a question that pauses Codex in an Orca chat reaches your devices with its options; an answer given in Orca withdraws it from your devices.
  • New notifai session status shows the name this computer gave the Agent Session you are in and where the name came from, so an agent can rename it when the name no longer fits its job.
  • Setup now approves every notifai command at once in Claude Code and Codex, so agents are no longer stopped by an approval prompt for a command the earlier list missed. An unchanged earlier Notifai approval is upgraded automatically; one you edited is left for you.

Bug Fixes

  • Codex question cards now reach your devices in every app, and your answer from a device reaches the agent even where it cannot close the card on screen. A card answer typed in Orca's chat or T3 Code closes the question on your devices.
  • An answer that arrives after you press Esc on a Codex turn now reaches the agent with nobody typing, or is handed in with your next prompt, and no longer runs an extra turn afterwards.
  • When Orca restarts a Codex conversation under another account, answers and notes now follow it to its new Codex home instead of waiting where nothing runs them, and wakes left behind in the old home are cleaned up; notifai doctor reports what was removed.
  • When you move a Claude Code conversation to the background, its open questions, answers and notes follow it to the background session instead of waiting on the old one.

View the CLI changelog on GitHub

Get the Mac beta: In Notifai, open Settings, then Updates, and choose Beta.

Get the Windows beta: In Notifai, open Settings, then Updates, and choose Beta.

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI · npm launcher

CLI 14.5.2-beta.1

What changed

  • After a temporary storage problem, Notifai keeps retrying cleanup so answers and notes can recover when storage is readable again.
  • A storage read failure can no longer let another process take over a delivery lock that may still be in use.
Full generated changelog

Sources for the summary

  1. Note 1: commit c0fe634
  2. Note 2: commit f83679a

Bug Fixes

  • Temporary storage read errors no longer stop Notifai from retrying cleanup. Once storage is readable again, cleanup resumes automatically instead of leaving delivery stuck until the process restarts.
  • A process that cannot read an existing delivery lock now leaves it alone, so another running process keeps ownership. Readable abandoned or malformed locks still recover normally.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI · npm launcher

CLI 14.5.1-beta.1

What changed

  • Setup finds the agent apps really installed, including Codex inside the ChatGPT app, and `notifai doctor` reports each one. Your devices say what is left to set up and when Codex still waits for hook approval.
  • `notifai project set` names a Project and gives it an avatar or icon, and agents name a new Project. Each computer appears once in Computers, and Settings › Devices turns notifications off for one device.
  • Fixed answers and notes that could wait for a Codex session, after a full disk, or beside a Claude Code background shell. Agents close a question you answered another way, and picker previews reach your devices.
Full generated changelog

Bug Fixes

  • An answer or note now reaches a Claude Code session that is resting at its prompt while a background shell it started is still running. Before, it waited until that shell ended, which could take as long as a dev server or a long build ran.
  • The "Not delivered yet" notification no longer arrives in the same moment your answer reaches the agent. The 5-minute bound now counts only the time the session was free to take your input, so a session that just finished working is never called stuck; the 30-minute bound still covers the whole wait. Once your input reaches the agent, a notification that said it hadn't is taken down from your devices.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI · npm launcher

CLI 14.5.0-beta.6

What changed

  • You can turn notifications off for one device. `notifai devices`, `doctor` and `init` show it as set up and off, not as something to fix.
  • Delivery recovers once a full disk has space again, and agents close a question you answered some other way or that no longer matters.
Generated changes since 14.5.0-beta.5

Sources for the summary

  1. Note 1: commit d72e0d4
  2. Note 2: commit 8946140 · commit a278484

Features

  • You can now turn notifications off for one device in your Companion Apps. notifai devices, notifai doctor and notifai init show that device as set up and off rather than as something to fix, and a notification sent while every device is off stays in your history and says no device was alerted.

Bug Fixes

  • If your disk filled up, answers and notes could stop reaching your sessions. Delivery now recovers once space is free, and notifai doctor checks that Notifai can save its delivery state and tells you when storage is full.
  • Agents now close a question you answered some other way, or one that no longer matters because its work is done, cancelled or replaced, instead of leaving it open on your devices.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

Earlier betas for 14.5.0 (4)

· Native CLI · npm launcher

CLI 14.5.0-beta.5

What changed

  • `notifai project set` gives a Project a name and an avatar or a catalog icon, and agents name a new Project the first time Notifai is enabled for it.
  • Answers and notes reach a waiting Codex session even after an account switch: Codex history no longer decides whether your input is delivered.
Generated changes since 14.5.0-beta.3

Sources for the summary

  1. Note 1: commit b616815 · commit 48a795e
  2. Note 2: commit fbdf642 · commit 0798d35

Features

  • New notifai project set gives a Project a display name and an avatar (a JPEG or PNG, resized on your computer) or a catalog icon with --icon; notifai project icons lists the choices. It won't overwrite a name or avatar you already set unless you pass --replace.
  • The first time Notifai is enabled for a Project, your agent is asked to give the Project a proper name, with the folder name in title case as the suggestion.

Bug Fixes

  • An answer or note could wait forever for a Codex session, for example after you switched accounts and Codex's session files moved to another place. Codex no longer decides whether your input is delivered: answers and notes now reach a waiting Codex session even after an account switch.

  • If an answer or note still hasn't reached its session after 5 minutes (30 minutes while the session is working), Notifai now sends you one plain notification saying so, and a question that gives up on its answer says so too, instead of waiting silently. Hermes no longer waits for an idle session before it starts listening for your answer.

  • Codex no longer shows a "Blocked by hook" line when a note or answer arrives while it is working on a turn.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI · npm launcher

CLI 14.5.0-beta.3

What changed

  • Each computer shows up once in your Computers list, with its operating system. Notifai sends only a hash of the computer’s identifier, never the identifier itself.
  • Signing in again on a computer that is already signed in now revokes the sign-in it replaces.
Generated changes since 14.5.0-beta.2

Sources for the summary

  1. Note 1: commit c086ff6
  2. Note 2: commit 29dbc2e

Features

  • Each computer now appears once in your Companion Apps' Computers list, however often it signs in. The CLI tells Notifai which computer it runs on, as a hash of your operating system's computer ID (the ID itself never leaves your computer), and which system it runs.

Bug Fixes

  • Running notifai login on a computer that is already signed in now signs out the sign-in it replaces, so the old one no longer stays in your Computers list.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI · npm launcher

CLI 14.5.0-beta.2

What changed

  • When Claude Code offers choices with previews, your devices show each choice’s preview too.
  • Notifai no longer wakes Codex in the middle of a running turn; it waits for the turn to end.
Generated changes since 14.5.0-beta.1

Sources for the summary

  1. Note 1: commit f64dce4 · commit 174a036 · commit c72c55c · commit 43c7969
  2. Note 2: commit 13b722a

Features

  • The option previews a Claude Code picker shows next to its choices now reach your phone and desktop with the question, so you can see what each choice means before you answer.

Bug Fixes

  • Codex no longer shows a "Blocked by hook" line when a note or answer arrives while it is working on a turn. Notifai now waits for the turn to end before it wakes Codex.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI · npm launcher

CLI 14.5.0-beta.1

What changed

  • Notifai now finds your agent apps by what is actually installed, including Codex bundled with the ChatGPT app, and notifai doctor reports what each one still needs.
  • A downloaded CLI update finishes installing on your next ordinary command, and notifai doctor treats a waiting update as ready instead of a problem.
  • Notifai’s apps can show what still needs setting up on each computer, including Codex hooks that are waiting for your approval.
Full generated changelog

Features

  • Setup now looks for the agent apps that are really installed on your computer. A leftover settings folder from an app you removed no longer counts, and Codex inside the ChatGPT app on Mac, and the Codex command on Windows, are recognised. A later notifai init offers an app you installed since, keeps your earlier choices (including "none") and skips an app name it doesn't know instead of failing.
  • notifai doctor now reports each agent app on its own: whether it is installed and connected, and what is still missing for it (hooks, approval, plugin or guidance), so a problem with one app no longer looks like a problem with all of them. notifai doctor --json carries the same report as agent_apps.
  • Notifai for Mac and Windows can now show what is left to set up on this computer: a one-line offer on Home to connect the agent apps it found, and an Agent apps page in Settings. Your Companion Apps also warn you when Codex is still waiting for you to approve Notifai's hooks, and the warning goes away once you approve them.

Bug Fixes

  • An update that was downloaded but is waiting for your running agent sessions to end now finishes by itself on the next notifai command once they have ended, checking at most once a minute so commands stay quick. Running sessions keep the version they started with, the automatic-update switch is respected, and an update that can't safely share your local data still waits for it to be safe.
  • notifai doctor no longer calls a downloaded update that is only waiting for sessions to end a problem to repair. It reports it as ready. An interrupted installation still asks for recovery.
  • If Notifai is interrupted just as a waiting update finishes, it still brings your installed skill and hooks up to date afterwards instead of forgetting that step.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI · npm launcher

CLI 14.4.2-beta.9

What changed

  • Fixed agents on Grok saying Notifai had blocked them. Notifai no longer holds back their first tool; its guidance now arrives whole with that tool’s result.
  • A Claude Code session now reaches your devices under the title Claude Code gives it, your rename included, instead of a generated name.
  • Agents show each answer or note that reached them through Notifai in the conversation, your words quoted exactly.
Generated changes since 14.4.2-beta.8

Sources for the summary

  1. Note 1: commit f7f7339
  2. Note 2: commit e9b94ac · commit c062c4d · commit 9606fcb
  3. Note 3: commit 0875632 · commit 42a4d0b

Features

  • Agents now show each answer, note or edit that reached them through Notifai in the conversation: a bold label line, your words verbatim in a quote, then one line naming the work it sets in motion.

Bug Fixes

  • On Grok, Notifai no longer holds back an agent's first tool to deliver its guidance. Grok showed the agent only the start of that text, so agents reported that Notifai had blocked them and never got the guidance. It now arrives whole with the first tool result.
  • A Claude Code session that sends without --session-label now reaches your devices under the title Claude Code gives it (your rename, else Claude Code's own title) instead of a generated name. A session already shown under a generated name takes that title once.
  • --session-label is never a usage error anymore: where the harness does not identify the Agent Session, Notifai sets the label aside with a one-line note and still sends. Agents name a session once, on their first send or ask.
  • Quoted replies keep each line apart in renderers that used to join them, such as Hermes' Markdown mode.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

Earlier betas for 14.4.2 (7)

· Native CLI · npm launcher

CLI 14.4.2-beta.8

What changed

  • `notifai channel` shows whether this computer follows Stable or Beta, and `notifai channel stable` or `notifai channel beta` switches it. Going back to Stable never installs an older build.
  • Notifai now refuses replies from the server with missing or malformed fields, with a clear error, instead of using them.
Generated changes since 14.4.2-beta.7

Sources for the summary

  1. Note 1: commit 902af72 · commit 90139e0
  2. Note 2: commit 064ce15 · commit 25dadaf · commit 26e832b

Features

  • notifai channel shows the release channel this computer follows, Stable or Beta, and notifai channel stable or notifai channel beta changes it (add --json for a machine-readable answer). Choosing Beta installs a newer beta at once. Choosing Stable keeps the build you have until a newer Stable release replaces it through automatic updates, and never installs an older build. notifai config explain updates.automatic shows whether automatic updates are on, and notifai config set updates.automatic false turns them off. Notifai for Mac and Windows carry the same two choices from their Settings.

Bug Fixes

  • Notifai handles unexpected answers from the server more safely: replies with missing or malformed fields are refused with a clear error instead of being used.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Beta release

Notifai update

  • CLI 14.4.2-beta.7 · native CLI · npm launcher

What changed

  • You can make a plain folder outside Git a Project on this computer with `notifai project folder add`. Agents working in it, or in a folder inside it, then send as that Project. The folder’s path stays on your computer.
  • Notifai for Mac 0.1.6 can do the same from Folders as Projects in its Settings once this beta is installed. The stable CLI doesn’t have folder Projects yet.
  • Fixed long questions from a Claude Code picker, Codex card or OpenCode reaching your devices as a fragment after an ellipsis. You now see the question being asked, with the full wording in the notification body, its lines and lists kept.
Generated changes since 14.4.2-beta.6

Features

  • A plain folder outside Git can now be a Project on this computer: notifai project folder add <path> --name <name>, with list, rename and remove (each takes --json). A send or ask from that folder, or any folder inside it, then carries that Project. A Git repository inside the folder keeps its own Project, and an explicit, configured or --projectless choice still wins. The folder's path never leaves the computer. Notifai for Mac 0.1.6 manages the same list under Folders as Projects in Settings.

Bug Fixes

  • A long Claude Code picker, Codex card or OpenCode question now reaches your devices as the question it asks: its last sentence ending in a question mark, else its closing whole sentences, never a fragment after an ellipsis. Its full wording goes into the Body with its lines kept and its bullet lines as a list, instead of one bold paragraph. Answers still map back to the exact picker wording.

Documentation

  • The Notifai skill tells agents to run notifai project folder add <path> --name <name> when you ask them to make a plain folder outside Git a Project.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI · npm launcher

CLI 14.4.2-beta.6

What changed

  • A Claude Code or Codex conversation T3 Code stopped after it sat idle now continues in its own T3 Code thread when your answer or note arrives, while T3 Code is running. Set `reopen.t3` to `off` to turn this off.
  • Each question in a `notifai ask --form` form can carry a short title and a Markdown detail on why it’s asked. Ordinary forms of up to 10 questions now fit a phone notification, and one too large is refused up front with what to shorten.
  • A question nobody answered now shows as expired on your devices instead of answered elsewhere. Notifai’s hooks also have short names now, shown while they run in Claude Code and in `/hooks` on new Codex installs.
Generated changes since 14.4.2-beta.5

Features

  • A conversation T3 Code stopped after it sat idle now continues by itself in its own T3 Code thread when an answer or note arrives, for Claude Code and Codex alike. It never continues in another thread or app and never starts T3 Code; while T3 Code is not running it waits for you as before. reopen.t3 (when-running by default, or off) controls it.
  • Each question of a notifai ask --form form can carry its own short title and an optional Markdown "detail" explaining why it is asked. Your devices show them with the question.
  • Notifai's hooks now have short names. Claude Code shows the name while a hook runs, and fresh Codex installs show them in /hooks. Codex installs that already carry an integration revision keep their approved hooks exactly as they are.

Bug Fixes

  • The agent in such a thread is told once to remind you to approve the hooks, with the step that works there: notifai doctor codex in a terminal on that machine, the same on every platform and app. In Orca one approval in ~/.codex covers every account. notifai init and its done message give the same step.

  • notifai ask refuses a form too large for a phone notification before registering it, with what to shorten, instead of letting it vanish. How much fits now depends on the Project's real name and avatar, so ordinary forms of up to 10 questions fit. notifai status says why a retired question ended.

  • A question nobody answered (Esc or "Chat about this" on Claude Code's picker, or the session ending) now shows as expired on your devices instead of answered elsewhere, and wording no longer calls the agent conversation "the terminal".

  • An unnamed Agent Session keeps a generated name until it is named, and a question opened through a harness picker no longer freezes that name.

  • A missing acknowledgement of an answer now holds an agent's turn for at most three Stops in a row in every case.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI · npm launcher

CLI 14.4.2-beta.5

What changed

  • New `notifai doctor codex` helps you approve Notifai’s Codex hooks. Run it in a terminal: it finds each Codex home where they still wait, such as a T3 Code account’s, and opens Codex’s own hook review there, with no sign-in.
  • In T3 Code, Orca and other apps that run Codex for you, the reminder to approve Notifai’s Codex hooks and `notifai init` now give `notifai doctor codex` as the step, the same on every platform, instead of a longer Codex command.
Generated changes since 14.4.2-beta.4

Sources for the summary

  1. Note 1: commit 3592ea9
  2. Note 2: commit 3592ea9

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

  • 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.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI · npm launcher

CLI 14.4.2-beta.4

What changed

  • After an update adds a hook, `notifai update --resume` and `notifai doctor` now name the hooks a running Codex session is missing and say a new Codex session picks them up, instead of calling the update done.
  • New Codex installs no longer add an `--integration-revision` argument to their hook commands. Existing installs keep their approved hooks exactly as they are, so nothing needs approving again.
Generated changes since 14.4.2-beta.2

Sources for the summary

  1. Note 1: commit e6bbe17
  2. Note 2: commit e6bbe17

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.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI · npm launcher

CLI 14.4.2-beta.2

What changed

  • Fixed Codex threads started in their own Codex home, such as a second account, never showing as running in the Notifai apps. They now show as running once they notify you.
  • When Notifai’s hooks aren’t approved for a Codex account, your agent now reminds you once with a command that opens Codex’s hook review for that account, with no sign-in. In T3 Code and Orca, run it in a terminal; on Windows it works in PowerShell.
  • Fixed approved Codex hooks being reported as still waiting for approval when ~/.codex is a symlink.
Generated changes since 14.4.2-beta.1

Sources for the summary

  1. Note 1: commit 794d7f4
  2. Note 2: commit c20a5a7 · commit 2407d05
  3. Note 3: commit d6a36b7

Bug Fixes

  • 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.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI · npm launcher

CLI 14.4.2-beta.1

What changed

  • Fixed Codex threads started in their own Codex home, such as a second account, never showing as running in the Notifai apps. They now show as running once they notify you.
  • When Notifai’s hooks aren’t approved for a Codex account, your agent now reminds you once at the end of its reply, with the exact command that approves them for that account.
Full generated changelog

Sources for the summary

  1. Note 1: commit 794d7f4
  2. Note 2: commit c20a5a7

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.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI · npm launcher

CLI 14.4.1-beta.1

What changed

  • Fixed answers waiting for your next message after a local write failed, for example on a full disk. Notifai now recovers on its own and keeps delivering answers to the session that asked.
Full generated changelog

Sources for the summary

  1. Note 1: commit f83bd34

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.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI · npm launcher

CLI 14.4.0-beta.1

What changed

  • Setup messages are easier to follow: one idea per paragraph, with the approval code on its own line and named links. On a Mac that already has the Notifai app, setup no longer suggests installing it.
  • Codex hook approval now says where to approve for the Codex you use: /hooks in the Codex CLI, or the Review hooks icon in the ChatGPT desktop app and the Codex editor extension. Your agent no longer waits for it; it carries on and reminds you at the end of its reply.
  • Fixed a loop where a conversation resumed after it had ended could make Notifai retry the same request about once a second.
Full generated changelog

Sources for the summary

  1. Note 1: commit 149c748 · commit 1e63329
  2. Note 2: commit 820d828
  3. Note 3: commit 27070e2

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.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI · npm launcher

CLI 14.3.0-beta.2

What changed

  • Sessions now take their real names from T3 Code and named Codex threads, replacing temporary names as soon as a real one exists.
Generated changes since 14.3.0-beta.1

Sources for the summary

  1. Note 1: commit abaccf8

Bug Fixes

  • An Agent Session takes its real name from T3 Code and from Codex's named threads, and a generated placeholder name is replaced as soon as a real one exists, without waiting for another notification.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

Earlier betas for 14.3.0 (1)

· Native CLI · npm launcher

CLI 14.3.0-beta.1

What changed

  • Setup asks one question: which agent apps to connect, and the answer is remembered.
  • Your browser opens and guides setup: approve this computer, then sign in on your phone by scanning a QR code. You only see the plan step when you need one, and approval codes now last 30 minutes.
  • Your agent waits for each step by itself, so you never have to tell it you're done, and setup messages are shorter.
Full generated changelog

Features

  • notifai init asks one question, which agent apps to connect (--apps <ids> or detected), then installs hooks, the skill and command approval for those apps; the answer is remembered.
  • Computer approval opens the approval page in the browser and keeps the same code open while setup waits; approval codes now stay valid for 30 minutes.
  • notifai init --json --wait <seconds> lets an agent's run wait for the User's step and report only new messages; setup messages are shorter.
  • After approval, the phone step follows the browser's setup page, including phone sign-in by QR; the plan step comes only when it is needed, and the setup notification is sent at most once.

Documentation

  • The Notifai skill runs setup as one waiting loop with a single apps question.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI · npm launcher

CLI 14.2.3-beta.5

What changed

  • Codex and Claude Code setup now recognizes shared configuration through symlinks, including account-manager homes. Codex explains when approval is needed through /hooks in the active home.
  • Notifai ignores Codex internal memory workspaces.
  • Setup keeps moving if its confirmation notification stalls, and asks about agent wiring before the phone step.
Generated changes since 14.2.3-beta.4

Sources for the summary

  1. Note 1: commit 7261b5f
  2. Note 2: commit 24da986
  3. Note 3: commit 545ede1 · commit 72b0a4b

Bug Fixes

  • Recognize shared Codex and Claude configuration through symlinks while preserving per-home Codex hook approval and explaining the /hooks approval step.
  • Exclude Codex internal memory workspaces.
  • Never let the setup confirmation notification hold up setup.
  • Ask about agent wiring before the phone step.

Build System

  • Consolidate publication into one resumable release workflow with immutable source admission and complete target installation acceptance.

Documentation

  • Show the iPhone app near the top of the README.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

Earlier betas for 14.2.3 (3)

· Native CLI · npm launcher

CLI 14.2.3-beta.4

What changed

  • Validates shared installation checks without a circular dependency; this build was never promoted to an update channel.
Generated changes since 14.2.3-beta.3

Sources for the summary

  1. Note 1: commit dba7331

Build System

All notable changes to this project are documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

This project follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html) and [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/).

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI · npm launcher

CLI 14.2.3-beta.3

What changed

  • Continues release-pipeline validation with retained immutable runtime source admission; this build was never promoted to an update channel.
Generated changes since 14.2.3-beta.2

Sources for the summary

  1. Note 1: commit 51f7430

Build System

All notable changes to this project are documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

This project follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html) and [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/).

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI · npm launcher

CLI 14.2.3-beta.2

What changed

  • A release-pipeline validation build, never promoted to the beta or stable update channels.
Full generated changelog

Sources for the summary

  1. Note 1: commit 35607fb

Build System

  • Validate the resumable CLI release pipeline without promoting discovery.

All notable changes to this project are documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

This project follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html) and [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/).

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI · npm launcher

CLI 14.2.2-beta.1

What changed

  • Phone setup uses a terminal QR, recognizes an installed app before a plan is active, and gives agents clear messages for remaining setup steps.
Full generated changelog

Sources for the summary

  1. Note 1: commit 2c1f178 · commit 9fa3baa · commit 3dbcdde

Bug Fixes

  • Show one plain line when sending or asking without a plan; finish phone setup before asking for a plan and avoid a setup notification without one.
  • Count an installed app with notification permission as set up while a plan is missing.
  • Show phone installation as a terminal QR without opening the computer browser.
  • Give every JSON setup gap a message for agents to relay as written, with matching setup guidance.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI · npm launcher

CLI 14.2.1-beta.2

What changed

  • Setup uses plainer messages and gives agents clearer instructions, including the Codex /hooks approval step.
Full generated changelog

Sources for the summary

  1. Note 1: commit 23b6e0b · commit 4d86f03

Bug Fixes

  • Retry propagation of Apple-accepted notarization tickets during release signing, retaining failed artifacts for diagnosis.
  • Ask optional setup questions after the test notification, use plainer approval and connection messages, and finish with one closing note.
  • Give agents explicit scripts for each setup moment and a plainer Codex /hooks request.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI · npm launcher

CLI 14.2.0-beta.2

What changed

  • Retries evidenced macOS notarization lookup failures while preserving strict rejection checks.
Generated changes since 14.2.0-beta.1

Sources for the summary

  1. Note 1: commit d31388b

Release reliability

  • Capture failed macOS notarization checks and retry only evidenced lookup failures; rejection and unknown errors remain fatal.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

Earlier betas for 14.2.0 (1)

· Native CLI · npm launcher

CLI 14.2.0-beta.1

What changed

  • Cursor uses its native conversation identity for sends, with more reliable session presence and notes. OpenClaw sessions retain their identity and notes.
Full generated changelog

Sources for the summary

  1. Note 1: commit 08bd30c · commit fdb29f9

Harness support

  • Identify Cursor conversations exactly for sends, maintain idle Session Presence on the macOS interactive CLI, and deliver notes without crossing prompt boundaries.
  • Identify OpenClaw sessions running on its Codex engine as OpenClaw, maintain Session Presence, and deliver notes.
  • Preserve OpenClaw notes when its prompt is rebuilt.

Release reliability

  • Vendor verified Bun license materials so native packaging does not depend on fetching them.
  • Bound npm-adapter verification phases with timeouts and process diagnostics.
  • Check agent guidance before builds and tests, and retain focused contract and routing regressions.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Beta release

Notifai update

  • CLI 14.1.0-beta.2 · native CLI · npm launcher

What changed

  • When an agent asks through a Codex or Grok question form that cannot reach your phone, it is told to ask through Notifai instead. In Claude Code and Codex, an answer the agent has not yet confirmed is repeated at its next prompt.
  • Grok no longer waits up to about 47 seconds per prompt when Claude Code is also set up on the same machine.
  • On Windows, Claude Code pickers and Codex cards now reach your phone too, under the same rules as macOS and Linux.
  • Hermes 0.21.5 and later gets its full session guidance. A session that another agent started with a task brief now reports to that agent instead of notifying you.
Generated changes since 14.1.0-beta.1

Features

  • An agent that asks through Codex's synchronous question form or Grok's question card is told the question never reached the User's devices and to ask with notifai ask. The form itself works as before.
  • notifai init --json returns the prepared sign-in approval message in technical.pairing.message, so an agent sends it as written.
  • notifai send notes on stderr when a Summary or Body is long enough to read poorly on a phone. The send, its exit code and its JSON are unchanged.

Bug Fixes

  • On Claude Code and Codex, an answer the agent has not yet acknowledged is restated at the next prompt, because neither harness honours a detached Stop hook's block.
  • When Grok runs with Claude Code or Cursor wired on the same machine, Grok's copies of their hooks end at once instead of starting the Notifai runtime, so Grok no longer waits up to about 47 seconds per prompt.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

Earlier betas for 14.1.0 (1)

· Native CLI · npm launcher

CLI 14.1.0-beta.1

What changed

  • On Windows, Claude Code pickers and Codex cards now reach your phone too, under the same rules as macOS and Linux.
  • Hermes 0.21.5 and later gets its full session guidance. A session that another agent started with a task brief now reports to that agent instead of notifying you.
Full generated changelog

Sources for the summary

  1. Note 1: commit de21573
  2. Note 2: commit 40bac51 · commit de82cd9

Features

  • Hermes agents receive the whole session guidance in two prompt sections on Hermes 0.21.5 and later; older Hermes keeps the single-section fallback.
  • Claude Code pickers and Codex cards link to the User's devices on Windows, under the same rules as macOS and Linux.

Bug Fixes

  • An Agent Session another agent started with a task brief reports to that agent and sends no Notification Requests unless the brief delegates them.
  • A claim release is no longer dropped while another process briefly holds its guard, so a close or hand-off never waits on a claim that was meant to be released.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI · npm launcher

CLI 14.0.0-beta.1

What changed

  • Agents get shorter, more consistent guidance, and your personal preferences remain under your control. Repository files no longer override Notifai configuration or guidance.
  • Waiting questions keep their native form in Claude Code and Codex on macOS and Linux, and reach your devices with a clear title, detail and images. OpenCode 1 forms carry the same context.
  • Disabled Projects stay quiet, and terminal answers clear the corresponding questions on your devices.
Full generated changelog

Sources for the summary

  1. Note 1: commit 73197cb
  2. Note 2: commit e77c910 · commit 54fc39f · commit cb32083
  3. Note 3: commit 69dde4b · commit 7411aa0

Breaking changes

  • Repository-supplied configuration and guidance are no longer read. Keep personal preferences in the User-owned machine or local Project settings.

Features

  • Ask and wait with notifai ask --wait; waiting Claude Code and Codex questions retain their native form and full device context.
  • Carry authored titles, standalone detail, images and choice descriptions through linked questions, including OpenCode forms and supported text and number pickers.
  • Record Codex terminal answers mechanically and keep disabled Projects silent across question routes.

Fixes

  • Load writing guidance at first use, simplify harness guidance, and prevent duplicate question registration.
  • Keep full notification content available when it does not fit in a push, and preserve close and approval behavior while terminal prompts are open.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Beta release

Notifai update

  • CLI 13.1.0-beta.7 · native CLI · npm launcher

What changed

  • Updating from 13.0.0 asks Codex to review only the hooks that are new or changed, so hooks you already trusted keep running. Rolling back to 13.0.0 keeps Claude Code questions working instead of leaving hooks it cannot read.
Generated changes since 13.1.0-beta.6

Bug Fixes

  • Updating from 13.0.0 or an earlier release asks Codex to review only the hooks that are actually new or changed, instead of all of them. Hooks the User already trusted keep running.
  • Rolling back to a release older than 13.1.0-beta.3 rewrites Claude Code hooks to a form that release can read, so questions keep working after the rollback and reinstalling the hooks no longer duplicates them. If the hooks cannot be rewritten, nothing is activated.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

Earlier betas for 13.1.0 (5)

· Beta release

Notifai update

  • CLI 13.1.0-beta.6 · native CLI · npm launcher

What changed

  • Questions stay open when an app unloads a conversation or your machine shuts down, restarts or crashes. A conversation you close ends its questions within seconds, and you can now dismiss any question from your phone.
  • When an answer arrives for a terminal conversation your machine stopped, Notifai reopens it with the same permissions; turn this off with notifai config set reopen.automatic off. Codex app conversations continue in the running app.
  • Fast and partial phone answers always reach the agent. Also fixed: concurrent sends, proxies, clock changes, nested repos and approving setup commands. Beta installs update when idle, or run notifai update.
Generated changes since 13.1.0-beta.5

Features

  • Each Claude Code and Codex session on macOS and Linux is now kept by a small native session helper, with one shared hub per user that talks to the service for all of them. At 25 sessions memory drops from about 600 MB to about 55 MB, the per-session process launches and credential reads every few seconds are gone, and a closed session's questions expire within seconds. Windows keeps the existing session attendant.

  • Closing an Agent Session ends its questions: they expire on every device, and an answer the agent had not read yet is dropped instead of being delivered later. The session's end record names any dropped answers.

  • Keep questions open when an app or the machine stops a conversation on macOS and Linux: the Claude desktop app pausing or evicting it, the Codex app or IDE unloading it, an idle T3 Code or Orca chat, an Orca terminal host dying, or the machine shutting down, restarting, crashing or losing power. The conversation is stopped, not closed: its questions stay open for their own windows, notes sent to it wait for it, and everything is handed in when it comes back.

  • Reopen a terminal conversation the machine stopped when its answer or note arrives: Notifai opens a new terminal window in the conversation's folder and resumes it with exactly the permissions it ran with, never more permissive ones, and never during a shutdown. If the permissions cannot be reproduced exactly, the conversation waits for the User instead. Turn it off with notifai config set reopen.automatic off; notifai doctor reports what reopen will do.

  • Continue a stopped Codex app conversation inside the running Codex app on macOS when its answer or note arrives, with no window, focus change or navigation. Notifai never starts the Codex app; turn this off with notifai config set reopen.codex_app off.

  • A question the User dismisses on a device ends at once: a Claude Code picker or a Codex card still on screen closes, notifai send --reply returns with exit 3, and the agent carries on without an answer.

  • A fork of a stopped conversation (Codex fork, Claude Code /branch) takes its questions and waiting answers with it when the service supports it.

Bug Fixes

  • Restart the shared hub seamlessly after any update, including notifai update, npm and installer updates, rollbacks, and hubs started by earlier builds: nothing a session waits for lives only in the hub any more, so only an update that changes the User's hooks waits. Until a hub hands over, notifai doctor and notifai update --check name the build it runs and what it is waiting for.

  • Confirm a session's end for about 10 seconds before expiring its questions, so a reload, a handoff to another window or app, codex resume, or a second terminal on the same conversation keeps them. This also applies on Windows and wherever no hub attends the session.

  • Fast and partial phone answers always reach the agent. A Claude Code picker answered within a second or two, answered only in part, with several replies or with typed text no longer stays open; an answer the picker cannot carry closes it and reaches the agent as its next message.

  • Keep concurrent sends from several agents in one Project from failing on shared state; every Notification Request is submitted exactly once.

  • Behind a proxy or a custom certificate authority, the shared hub now reaches the service and answers arrive. The hub takes its network settings from sign-in and nothing else from the shell that started it, so API keys and tokens no longer reach it.

  • On Linux, a clock change (a network time step after resume, a VM clock correction) no longer makes running sessions look gone.

  • A submodule, nested clone or worktree inside a configured Project now belongs to that Project, and a loose config file in a plain parent folder no longer swallows every repository below it. The home folder is never a Project.

  • Setup inside a fresh Claude Code session keeps the User's yes to command approval. Command approval is offered only in Claude Code's default permission mode, and an explicit --claude-commands that adds nothing says why.

  • In Codex, notifai ask asks an ordinary question when the session has no question card, instead of pointing the agent at a tool it does not have.

  • A shell that inherited an agent session's markers, such as a tmux server or editor started from that session, no longer sends its questions into that session.

  • Back off wakes when the agent cannot take its input in, from 5 seconds up to 5 minutes, instead of starting a turn every second during an outage.

  • An idle Codex terminal on the shared server is woken only while a terminal shows the conversation, after a one-time behaviour check of that Codex version.

  • Keep Notifai's Codex control connection from labelling the User's own Codex threads.

  • Keep a Claude Code picker in a second window linked when the first window exits.

  • Settle hook repair requirements against the hook definition actually present, and give one Codex hook trust line per hooks file with a step the User can take.

  • Keep Claude Code hooks on the shared hub instead of starting the runtime for every hook, and recover a question claim left by a crashed process at once.

  • notifai config rows fit the terminal.

  • Never revive a closed session headlessly: Claude Code cold resume (claude -p --resume) is removed, and a stopped conversation reopens only in a visible terminal.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Beta release

Notifai update

  • CLI 13.1.0-beta.5 · native CLI · npm launcher

What changed

  • After you update Notifai, with notifai update, npm or the install script, the shared session helper now moves to the new version as soon as nothing is waiting, including helpers started by earlier betas.
  • Until it moves, notifai doctor and notifai update --check tell you which version the helper is still running and what it is waiting for.
Generated changes since 13.1.0-beta.4

Bug Fixes

  • Hand the shared session hub over to the active build after any update, including notifai update, npm and installer updates, rollbacks, and hubs started by earlier builds, as soon as nothing is waiting. Until then notifai doctor and notifai update --check name the build the hub runs and what it is waiting for.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Beta release

Notifai update

  • CLI 13.1.0-beta.4 · native CLI · npm launcher

What changed

  • Notifai now keeps itself up to date on macOS and Linux, on your chosen channel. It never installs while a question is waiting and never moves you to an older version. Turn it off with notifai config set updates.automatic off --yes.
  • Your agents respond faster: frequent hooks are answered by the already-running Notifai helper. After an update, older answer processes hand your questions over, and idle Claude Code sessions stay reachable.
  • OpenCode's own question form now reaches your devices, and OpenClaw, Hermes and Grok are steadier. Codex no longer starts empty turns for stale wake-ups, and idle Codex app conversations stay answerable.
Generated changes since 13.1.0-beta.3

Features

  • OpenCode's own question form now reaches the User's devices, and whichever answer comes first, from a device or in OpenCode, settles it. OpenClaw applies a changed plugin to a running Gateway and hands sessions over cleanly on reload, Hermes uses only the public plugin interface and holds writes while an approval prompt or session command is open, and Grok's question route is requalified.
  • Install CLI updates automatically on macOS and Linux through the shared hub, at most once a day, on the saved channel and never to an older build. An update never activates while a question, answer, note or acknowledgement is pending. Turn it off for the whole machine with notifai config set updates.automatic off --yes.
  • Answer the frequent Claude Code and Codex hooks from the running hub through the native launcher on macOS and Linux instead of starting the runtime each time, making warm hooks several times faster.
  • Block empty Codex wake-ups that no longer have anything to deliver, so they start no turn; a human prompt is never blocked. Codex app and IDE conversations that Codex unloads after 30 minutes idle stay open and answerable.

Bug Fixes

  • Hand a session's questions to one current answer owner, so an answer process started by an older version no longer holds them after an update.
  • Keep idle Claude Code sessions started on an older version attended after an update: the switch to exec-form hooks waits until those sessions hand over.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Beta release

Notifai update

  • CLI 13.1.0-beta.3 · native CLI · npm launcher

What changed

  • Notifai now runs much lighter on macOS and Linux: each agent session gets a tiny helper and one shared hub talks to Notifai for all of them, so many open sessions use a fraction of the memory and no longer start processes every few seconds.
  • When you close an agent session, its questions now disappear from your devices within a second or two. In Claude Code 2.1.139 and newer, Notifai's hooks start faster because they no longer go through a shell.
  • Codex question cards now link to your devices only with Codex 0.163.0 or newer; older Codex asks a plain question instead. Setup and other interactive screens also display correctly in terminals that report no width.
Generated changes since 13.1.0-beta.2

Features

  • Each Claude Code and Codex session on macOS and Linux is now kept by a small native session helper, with one shared hub per user that talks to the service for all of them. At 25 sessions memory drops from about 600 MB to about 55 MB, the per-session process launches and credential reads every few seconds are gone, and a closed session's questions expire within one to two seconds. Windows keeps the existing session attendant.

  • Claude Code hooks run in exec form on Claude Code 2.1.139 and newer, and stay in shell form on older versions; notifai doctor reports the hook form and the shared hub.

  • Codex question cards link to devices only with Codex app-server 0.163.0 or newer; older Codex falls back to an ordinary question, and a daily canary checks that card linking still works.

Bug Fixes

  • Lay out interactive screens on a terminal that reports zero width.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Beta release

Notifai update

  • CLI 13.1.0-beta.2 · native CLI · npm launcher

What changed

  • Closing an agent session now ends its questions: they disappear from your phone and other devices at once, and an answer the agent had not read yet is dropped instead of arriving later. Notifai never reopens a closed session.
  • Codex can send your questions and updates without waiting at a terminal approval: on your yes, notifai init --codex-commands allows only the everyday Notifai commands outside the Codex sandbox.
  • Hooks stay inside their time limits, so slow credential or update checks no longer hold up your prompt, and Codex question cards reach your devices from the card itself without leaving a stray question open.
Full CLI changelog for 13.1.0-beta.2

Features

  • Closing an Agent Session ends its questions: they expire on every device at once, and an answer the agent had not read yet is dropped instead of being delivered later. The session's end record names any dropped answers.
  • Let Codex run Notifai commands outside its sandbox on the User's yes: notifai init --codex-commands writes a Codex rule that allows only the everyday Notifai commands, notifai doctor reports codex-commands readiness, and notifai hooks uninstall --harness codex removes the rule.

Bug Fixes

  • Never revive a closed session. Claude Code cold resume (claude -p --resume) is removed; idle but open sessions still receive their answers, and the delivery contracts shown by doctor say so.
  • Keep every hook inside its own timeout: credential reads happen only when a hook actually calls the service, nested steps get a budget derived from the hook's declared timeout, and session pruning and update checks run in a detached daily maintenance process instead of on the prompt path.
  • Register Codex questions from the native question card itself, so an answered card no longer leaves a separately copied question pending.
  • Report integration health only for the active native build, so a retained older runtime can no longer surface stale CLI or skill faults in current hooks.
  • Beta updates always choose the newer of the beta and stable releases.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Beta release

Notifai update

  • CLI 13.0.0-beta.1 · native CLI · npm launcher

What changed

  • In Claude Code, every question picker an agent opens in an enabled Project now reaches your phone and other devices by itself. Answer on your phone and the picker in the terminal closes.
  • Answer in the terminal and your devices stop asking; press Esc or choose to chat and the question disappears from them. Breaking: in Claude Code, notifai ask now declines questions the picker can ask, so you are never asked twice.
  • Also includes the 12.1.2 beta fixes: smoother back-to-back answers, lighter waiting, better Grok support, a doctor that judges only its own harness, and skill copies that stay current.
Full CLI changelog for 13.0.0-beta.1

⚠ BREAKING CHANGES

  • In a Claude Code session with Notifai's picker hooks installed, notifai ask refuses a question the question picker can show (code use_question_picker, exit 2) and returns the AskUserQuestion input to use instead. It no longer returns native_question for Claude Code.

Features

  • Make the Claude Code question picker the question: every picker in an enabled Project reaches the user's devices by itself, and a device answer closes it. A terminal answer is recorded so devices stop asking; Esc or chatting instead withdraws the device question. Question and hook outcomes are kept in a slower-rotating events log that notifai logs reads.

Bug Fixes

  • Log project-not-enabled when a picker stays in the terminal because its Project is not enabled.

  • Judge doctor, setup and update readiness for the harness that runs them: another harness's condition is reported as not applying and no longer fails the session, and a missing Codex shared app-server no longer turns Question Routing readiness off.

  • Keep every Notifai skill copy current: setup and updates refresh any outdated copy in a harness skill location in place, a linked skill directory counts as one copy, and project-scope writes stay inside the project.

  • Repair Grok activation and question delivery across main sessions, subagents, resume, compaction, long answers and interrupted turns.

  • Support continuing questions, Session Notes and Answer Edits in an existing Grok shared-leader session, with exact-session delivery claims and acknowledgements.

  • Avoid duplicate imported Notifai hooks and explain how to disable incompatible Cursor hook imports in Grok.

  • Hold unanswered reply requests longer and back off after concurrent-wait limits, reducing repeated requests while an agent waits.

  • Stop watching retired questions while preserving prompt answers to concurrent questions and recovering replies received near a wait deadline.

  • Keep remote question conversations flowing after three acknowledged answers, while preserving retry protection for the same answer.

  • Distinguish scheduled question submission from confirmed submission and delivery.

  • Settle questions answered through native harness forms so they do not remain outstanding.

Documentation

  • Clarify Grok capabilities and limits; improve the package setup README and npm discovery metadata.

  • Direct invited Android testers to the Google Play closed Alpha instructions.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Beta release

Notifai update

  • CLI 12.1.2-beta.4 · native CLI · npm launcher

What changed

  • notifai doctor now checks only the harness it runs in. Another harness's problem is listed as not applying, and a missing Codex shared server no longer turns question routing off.
  • Every Notifai skill copy stays current: updates and setup refresh outdated copies in Claude Code, Codex, Cursor, OpenCode, Grok, Hermes and OpenClaw, and a symlinked skills folder counts as one copy.
Generated changes since 12.1.2-beta.3

Bug Fixes

  • Judge doctor, setup and update readiness for the harness that runs them: another harness's condition is reported as not applying and no longer fails the session, and a missing Codex shared app-server no longer turns Question Routing readiness off.
  • Keep every Notifai skill copy current: setup and updates refresh any outdated copy in a harness skill location in place, a linked skill directory counts as one copy, and project-scope writes stay inside the project.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

Earlier betas for 12.1.2 (3)

· Beta release

Notifai update

  • CLI 12.1.2-beta.3 · native CLI · npm launcher

What changed

  • Grok receives Notifai guidance reliably, including after resuming or compacting a session.
  • Questions return to the right Grok session. Sessions started with grok --leader can also receive Notes and Answer Edits while idle.
  • Imported Notifai hooks no longer run twice when Grok also loads Claude or Cursor configuration.
Generated changes since 12.1.2-beta.2

Bug Fixes

  • Repair Grok activation and question delivery across main sessions, subagents, resume, compaction, long answers and interrupted turns.
  • Support continuing questions, Session Notes and Answer Edits in an existing Grok shared-leader session, with exact-session delivery claims and acknowledgements.
  • Avoid duplicate imported Notifai hooks and explain how to disable incompatible Cursor hook imports in Grok.

Documentation

  • Clarify Grok capabilities and limits; improve the package setup README and npm discovery metadata.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Beta release

Notifai update

  • CLI 12.1.2-beta.2 · native CLI · npm launcher

What changed

  • Agents waiting for an answer make fewer requests and back off when the service is busy.
  • Finished questions stop their reply watchers, while other questions can still receive answers promptly.
Generated changes since 12.1.2-beta.1

Bug Fixes

  • Hold unanswered reply requests longer and back off after concurrent-wait limits, reducing repeated requests while an agent waits.
  • Stop watching retired questions while preserving prompt answers to concurrent questions and recovering replies received near a wait deadline.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Beta release

Notifai update

  • CLI 12.1.2-beta.1 · native CLI · npm launcher

What changed

  • Keep answering questions from your devices without returning to the terminal after three replies.
  • Question status now clearly distinguishes scheduled submission from confirmed sending and delivery.
  • Questions answered through native agent forms settle correctly instead of remaining outstanding.
Full CLI changelog for 12.1.2-beta.1

Bug Fixes

  • Keep remote question conversations flowing after three acknowledged answers, while preserving retry protection for the same answer.
  • Distinguish scheduled question submission from confirmed submission and delivery.
  • Settle questions answered through native harness forms so they do not remain outstanding.

Documentation

  • Direct invited Android testers to the Google Play closed Alpha instructions.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Beta release

Notifai update

  • iPhone 1.1 · TestFlight · build 67
  • Android 0.1.0 · Firebase App Distribution · build 43

What changed

  • New notifications, sessions and questions now glide into place instead of popping in.
  • Answering a question flows smoothly, from the send countdown to the agent's reply.
  • Livelier taps and screen transitions on iPhone and Android, with subtle haptic feedback.

Update the iPhone app: Open TestFlight.

Update the Android app: Use your Firebase App Distribution invitation.

· Native CLI · npm launcher

CLI 12.1.1-beta.2

What changed

  • Answers now wake idle Claude Code sessions even when their inbox was still starting when Notifai connected.
Generated changes since 12.1.1-beta.1

Sources for the summary

  1. Note 1: commit 6b1d6dc

Bug Fixes

  • Wake idle Claude Code sessions whose inbox was still starting when Notifai began attending them.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

Earlier betas for 12.1.1 (1)

· Native CLI · npm launcher

CLI 12.1.1-beta.1

What changed

  • Answers from your devices now wake idle Claude Code sessions that use a custom configuration directory.
Full generated changelog

Sources for the summary

  1. Note 1: commit 1ea5293

Bug Fixes

  • Wake idle Claude Code sessions with answers from your devices when CLAUDE_CONFIG_DIR relocates Claude's configuration.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI · npm launcher

CLI 12.1.0-beta.3

What changed

  • Answers and notes recover after signing in again, without repeated empty wakes or restarting your agent.
  • Notifications keep their Project when an agent works from a temporary folder.
  • Setup detects your installed harnesses, and Mac sign-in handles non-ASCII machine names.
Full generated changelog

Sources for the summary

  1. Note 1: commit 5fc5d42
  2. Note 2: commit 5fc5d42
  3. Note 3: commit 4e4a2a9 · commit 4e2f7bb · commit cbe5591

Features

  • Show detected harnesses in setup results.

Bug Fixes

  • Recover session delivery when this machine signs in again, preserving queued input and active agents.
  • Suppress repeated wakes while input delivery is refused, and resume after fresh attendance.
  • Preserve the session's Project when sending from a temporary directory; directories outside Git no longer become inferred Projects.
  • Read back Keychain credentials with non-ASCII machine names.
  • Recognize the desktop app as a Companion App during setup.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Beta release

Notifai update

  • iPhone 1.0 · TestFlight · build 64
  • Android 0.1.0 · Firebase App Distribution · build 41

What changed

  • Smoother iPhone timelines with more reliable read states, image galleries, and replies.
  • New default notification sounds on iPhone and Android.
  • A simpler handoff to finish computer setup.

Update the iPhone app: Open TestFlight.

Update the Android app: Use your Firebase App Distribution invitation.

· Native CLI · npm launcher

CLI 12.0.0-beta.21

What changed

  • Linux credentials remain usable across desktop and headless sessions without reviving cleared credentials.
  • Updates from earlier native runtimes can stage safely and resume after incompatible sessions finish, preserving their pending work.
Generated changes since 12.0.0-beta.20

Sources for the summary

  1. Note 1: commit 9e349a8
  2. Note 2: commit 6614fc8

Fixes

  • Preserve existing Linux file credentials across desktop and headless sessions. Keep secure credential authority explicit and prevent cleared keyring credentials from reappearing.
  • Stage and resume a verified transition from earlier native runtimes without losing pending work or allowing incompatible writers to overlap.

Improvements

  • Include the current desktop Companion connection and one-sign-in support in the CLI candidate. Desktop app distribution remains separate.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

Earlier betas for 12.0.0 (10)

· Beta release

Notifai update

  • CLI 12.0.0-beta.20 · native CLI · npm launcher

What changed

  • Windows migration now allows enough time to verify slower npm installations before changing them.
  • Codex questions use native forms only when Notifai can reach their owning session, preventing disconnected forms from staying pending after a reply.
Generated changes since 12.0.0-beta.19

Fixes

  • Allow Windows repair enough time to verify a complete Node/npm installation, while preserving all trust checks and a bounded package-manager lifetime.
  • Create a linked Codex question form only when the owning app-server can receive its answer; otherwise keep the question in the ordinary reply flow.
  • Restore the Codex app-server connection from compiled native builds and allow for cold starts.

View the CLI changelog on GitHub

Update the CLI beta: Follow the one-time upgrade instructions for older installations.

· Beta release

Notifai update

  • CLI 12.0.0-beta.19 · native CLI · npm launcher

What changed

  • Old session records no longer hold the first native upgrade indefinitely. Their contents stay intact, and activation still waits for live work to finish.
Generated changes since 12.0.0-beta.17

Fixes

  • Preserve understood dormant session records during native activation instead of letting old cleanup and ended-session work block updates indefinitely. Live owners, undelivered input and uncertain state still hold activation.
  • Allow a verified standalone installer to abandon an uncommitted first upgrade before the permanent writer fence, so a corrected candidate can replace it safely.

View the CLI changelog on GitHub

Update the CLI beta: Follow the one-time upgrade instructions for older installations.

· Beta release

Notifai update

  • CLI 12.0.0-beta.17 · native CLI · npm launcher

What changed

  • Windows repair can now proceed after applications are paused, instead of mistaking its own waiting package manager for an unknown process.
Generated changes since 12.0.0-beta.16

Fixes

  • Allow Windows npm repair to recognize its own suspended package manager before Windows initializes the process module list. Other readers and mismatched process identities still prevent replacement.

View the CLI changelog on GitHub

Update the CLI beta: Follow the one-time upgrade instructions for older installations.

· Beta release

Notifai update

  • CLI 12.0.0-beta.16 · native CLI · npm launcher

What changed

  • Shell, PowerShell, npm and npx use one native CLI, with release notes included in the binary.
  • Compatible updates preserve existing questions and session owners. Changed owned hooks are repaired while user-managed files stay intact.
  • Agents can repair verified old Windows npm installations in place and recover interrupted replacement without uninstalling first.
Generated changes since 12.0.0-beta.15

Fixes

  • Keep active questions and session owners on compatible retained runtimes during native updates. Stage incompatible first upgrades until existing work can finish safely.
  • Repair verified legacy Windows npm installations in place through their package manager during an approved observed maintenance window. Preserve the complete package and recover interrupted replacement forward without uninstalling first.
  • Repair only changed owned harness integration, preserve User edits and healthy owners, and recover abandoned Hermes publication reservations without replaying host operations.
  • Report the actual CLI execution domain and scoped pending repair in diagnostics.
  • Compile Windows PowerShell bootstrap helpers correctly when temporary paths contain Unicode, quotes or shell punctuation.

View the CLI changelog on GitHub

Update the CLI beta: Follow the one-time upgrade instructions for older installations.

· Beta release

Notifai update

  • CLI 12.0.0-beta.15 · native CLI · npm launcher

What changed

  • Shell, PowerShell, npm and npx use the same native CLI, with updates managed through notifai update.
  • Updates refresh installer-owned guidance and recover owned hooks and sessions while preserving unrelated user-installed skills.
  • Native updates now include readable release notes inside the CLI.
Generated changes since 12.0.0-beta.13

Improvements

  • Include readable release notes in every native binary and verify the bundled changelog against canonical source.

  • Verify npm publication using its current dist-tag endpoint, with bounded reads and no repeat publication or unrelated tag changes.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Beta release

Notifai update

  • CLI 12.0.0-beta.13 · native CLI · npm launcher

What changed

  • Shell, PowerShell, npm and npx use the same native CLI, with updates managed through notifai update.
  • Updates refresh installer-owned guidance and recover owned hooks and sessions while preserving unrelated user-installed skills.
  • Codex activity tracking can resume across oversized transcript entries without resetting existing sessions.
Generated changes since 12.0.0-beta.11

Improvements

  • Refresh installer-owned guidance and recover owned hooks and sessions even when unrelated user-installed skills are present; preserve those files and keep their diagnosis visible.
  • Wait briefly for npm publication metadata to propagate without retrying publication or accepting unrelated tag changes.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Beta release

Notifai update

  • CLI 12.0.0-beta.11 · native CLI · npm launcher

What changed

  • Shell, PowerShell, npm and npx use the same native CLI, with updates managed through notifai update.
  • Codex activity tracking can resume across oversized transcript entries without resetting existing sessions.
  • Doctor, setup and update consistently identify installer-owned and user-managed guidance; existing user files are preserved.
  • Known beta issue: mixed managed and user-installed skills can leave update integration pending. Existing guidance stays intact; a correction is in progress.
Generated changes since 12.0.0-beta.8

Improvements

  • Resume Codex activity tracking across oversized transcript entries without resetting existing sessions.
  • Give doctor, setup and update the same skill ownership diagnosis; preserve user-managed content and recover interrupted installer-owned placements.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Beta release

Notifai update

  • CLI 12.0.0-beta.8 · native CLI · npm launcher

What changed

  • Shell, PowerShell, npm and npx use the same native CLI. Windows npm startup avoids repeated PowerShell launches; notifai update manages the runtime and its channel.
  • Doctor gives clear installation and old npm migration recovery steps, while unfinished removal stays resumable without discarding pending work.
  • Notes can reach agents during long Codex sessions, and Claude Code question pickers link to the matching question without copied title markers.
Generated changes since 12.0.0-beta.6

Improvements

  • Batch Windows npm permission verification instead of starting one PowerShell process per package path. Keep signed payload checks and reject unsafe members.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI · npm launcher

CLI 12.0.0-beta.6

What changed

  • Shell, PowerShell, npm and npx use the same native CLI. npm manages only its launcher; notifai update manages the runtime and its channel.
  • Doctor gives clear installation and old npm migration recovery steps, while unfinished removal stays resumable without discarding pending work.
  • Notes can reach agents during long Codex sessions, and Claude Code question pickers link to the matching question without copied title markers.
Generated changes since 12.0.0-beta.5

Sources for the summary

  1. Note 1: commit a866a72 · commit 74df008
  2. Note 2: commit f8f6291
  3. Note 3: commit 151ba68 · commit 449a4eb

No new changelog entries compared with the previous beta.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI · npm launcher

CLI 12.0.0-beta.5

What changed

  • Shell, PowerShell, npm and npx use the same native CLI. npm manages only its launcher; notifai update manages the runtime and its channel.
  • Doctor gives clear installation and old npm migration recovery steps, while unfinished removal stays resumable without discarding pending work.
  • Notes can reach agents during long Codex sessions, and Claude Code question pickers link to the matching question without copied title markers.
Full generated changelog

Sources for the summary

  1. Note 1: commit a866a72 · commit 74df008
  2. Note 2: commit f8f6291
  3. Note 3: commit 151ba68 · commit 449a4eb

Breaking changes

  • The existing @raidiant/notifai npm package now installs and launches the managed native CLI instead of shipping a separate Node runtime. Existing native installations keep their version and channel until an explicit update.

Improvements

  • Verify npm-owned Windows directories and account profiles without changing their ACLs, while preserving strict ownership of managed native paths.

  • Use the same native runtime and bundled skill through shell, PowerShell, npm, and npx setup.

  • Report installation ownership and recovery clearly in doctor, preserve unfinished removal, and make migration from older npm installations explicit.

  • Continue interactive setup correctly when installing through a piped shell command.

  • Verify npm adapter bytes against the signed native release and coordinate publication across all supported targets.

  • Keep long Codex turns readable and link Claude question-picker content to its registered question.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Beta release

Notifai update

  • CLI 11.8.1-beta.1 · native download

What changed

  • Long Codex sessions keep their activity state as transcripts grow, helping Notes reach agents reliably during extended work.
  • Updating can recover progress in long sessions while preserving pending input and existing approvals.
Full CLI changelog for 11.8.1-beta.1

Bug Fixes

  • cli: preserve native activity verification during long Codex turns and recover bounded transcript progress during updates (#276) (151ba68)

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Beta release

Notifai update

  • CLI 11.8.0-beta.7 · native download

What changed

  • Notes can now be read on slower connections without timing out or getting stuck behind an earlier delivery.
  • Install and update Notifai on macOS, Linux or Windows without Node or npm, including Windows folders left by the old CLI.
  • Claude Code gets reliable wake-ups, linked question pickers and a native Windows inbox; open sessions can move to the updated CLI.
Generated changes since 11.8.0-beta.5

Features

  • Install and update the standalone native CLI without a Node.js runtime.
  • Use the Claude Code session inbox on Windows, link registered questions to the native question picker, and keep session names in sync with Claude Code titles.

Bug Fixes

  • Allow foreground Note reads to survive ordinary network latency, and recover earlier delivery reports without preventing the next Note from being read.
  • Preserve open Claude Code sessions when updating the native runtime.
  • Refresh and verify the skill copy each harness loads, and keep explicit questions and owed answers independent of Project Enablement.
  • Install over folders left by older Windows installations and use native installation guidance.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

Earlier betas for 11.8.0 (4)

· Beta release

Notifai update

  • CLI 11.8.0-beta.5 · native download

What changed

  • Install and update Notifai on macOS, Linux or Windows without Node or npm. Agents now reuse the native CLI instead of restoring the old npm runtime.
  • Fixes dropped Claude Code wake-ups and lets open sessions move to the updated CLI.
  • Windows installation now handles folders left by the old npm CLI, and native commands are easier to find across shells.
Generated changes since 11.8.0-beta.4

Bug Fixes

  • When an agent cannot find Notifai on PATH, look for the existing native CLI before installing. Native installation instructions replace the frozen npm-runtime fallback, which could shadow an updated installation.

Dependencies and limits

All notable changes to this project are documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

This project follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html) and [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/).

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI download

CLI 11.8.0-beta.4

What changed

  • Install Notifai on macOS, Linux or Windows without Node or npm, with native updates that stay on your chosen release channel.
  • Fixes dropped Claude Code wake-ups and lets open sessions move to the updated CLI.
  • Windows installation now handles folders left by the old npm CLI, and native commands are easier to find across shells.
Generated changes since 11.8.0-beta.3

Sources for the summary

  1. Note 1: commit 91ece1b
  2. Note 2: commit a431bf5 · commit 3383813 · commit cb3e6dc
  3. Note 3: commit 809aa85 · commit 02fdb1e

Bug Fixes

  • Install on Windows over the ~/.notifai folder an earlier npm CLI left behind. 11.8.0-beta.3 refused it as unsafe before migrating its permissions.

Dependencies and limits

  • 11.8.0-beta.1 was tagged but never published. 11.8.0-beta.2 and 11.8.0-beta.3 were published with the defects above; update to this beta with notifai update.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI download

CLI 11.8.0-beta.3

What changed

Features

  • Put the notifai command in the User command directory ($XDG_BIN_HOME or ~/.local/bin), as Claude Code's native installer, uv and pipx do. A shell startup file is edited only when that directory is not already on PATH (zsh, bash, sh and fish); other shells get the exact line to add instead of an error.

Bug Fixes

  • Order session lifecycle events written by different processes correctly in the native runtime. In 11.8.0-beta.2 its clock restarted in every process, so an open session did not hand over to a newly installed runtime and Codex session ownership checks were unreliable.

Dependencies and limits

  • 11.8.0-beta.1 was tagged but never published. 11.8.0-beta.2 was published with the clock defect above; update to this beta with notifai update.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Native CLI download

CLI 11.8.0-beta.2

What changed

Features

  • Install and update Notifai as a standalone native CLI on macOS, Linux and Windows. The runtime needs no Node, npm, Bun or Git, verifies signed release inventories, and follows a signed beta update channel.
  • Link registered questions to the Claude Code question picker.
  • Use the Claude Code session inbox on native Windows.
  • Name a Claude Code Agent Session from the session's own title.
  • Offer Claude Code approval for the commands an away User needs.

Bug Fixes

  • Give each Claude Code wake its own token. Claude Code drops a message identical to the previous one, so a repeated wake to an idle session never arrived.
  • Hand an open Claude Code session over to the installed runtime at its next prompt or turn end, so a session open across an update no longer keeps the previous wake behavior.
  • Open Claude Code inbox writes with the session token.
  • Refresh and verify the skill copy each harness loads.
  • Keep explicit questions and owed answers independent of Project Enablement.

Dependencies and limits

  • Protocol stays at 8.2.1.
  • Native archives embed Bun 1.4.2. Its corresponding source is the runtime-sources-bun-1.4.2 release, and every archive carries the notices and rebuilding instructions.
  • macOS executables are Developer ID signed and notarized. Windows executables are unsigned in this beta.
  • This beta is distributed as native archives through the shell and PowerShell bootstraps or a manual download. It is not published to npm, and the optional npm bootstrap is not yet available.
  • An existing npm installation moves to the native runtime only through the explicit migration step; it is never replaced automatically.
  • 11.8.0-beta.1 was tagged but never published: its release scripts failed against the real macOS signing tools and GitHub API before any artifact shipped. This is the first published 11.8.0 beta.

View the CLI changelog on GitHub

Update the CLI beta: notifai update --channel beta · Native installation

· Beta release

Notifai update

  • iPhone 1.0 · TestFlight · build 63
  • Android 0.1.0 · Firebase App Distribution · build 40

What changed

  • Approve a computer from an onboarding QR code in Notifai.
  • Keep native-question answers, edits and acknowledgements attached to the right submission.

Update the iPhone app: Open TestFlight.

Update the Android app: Use your Firebase App Distribution invitation.

· CLI beta on npm

CLI 11.7.1-beta.2

What changed

Bug Fixes

  • Retry transient Windows lock-directory deletion before contender publication, while preserving bounded access checks and fatal failures after publication.

Features

  • Includes linked Codex question answers, hook-delivered input, reconciled idle wakes, and QR-first computer approval from the preceding beta.

View the CLI changelog on GitHub

Get the beta CLI: notifai update --channel beta

· CLI beta on npm

CLI 11.7.0-beta.2

What changed

  • Answer linked questions in Codex or Notifai, with each submission and acknowledgement kept clear.
  • Replies reach working agents through hooks, with fewer stale inbox prompts after input has already arrived.
  • Approve a computer with a QR code, including from text-only terminals.
Full generated changelog

Sources for the summary

  1. Note 1: commit 182f2cc
  2. Note 2: commit 03cedba · commit 0c2add8
  3. Note 3: commit 6e80bab · commit 21439ff

Features

  • Synchronize explicitly linked Codex questions with app answers while preserving unrelated native forms, distinct submissions, and answer acknowledgements.
  • Approve a computer through QR-first setup, including text-only terminal QR presentation.

Bug Fixes

  • Deliver input through working-turn hooks and defer wakes until native turn completion; reconcile only exact owned stale queue entries.
  • Keep settled question IDs usable for explicit closure without repeating acknowledgement.
  • Avoid redundant permission changes when writing private local state.

Dependencies and limits

  • Update the WebSocket client to 8.21.0 to address published security advisories.
  • Pin protocol 8.2.0-beta.2, including native-answer capability discovery and reporting.
  • Live optional Codex native-control acceptance is limited to macOS Codex 0.160.0. Uncertain writes retain recovery state; cancellation can lose to dequeue.

View the CLI changelog on GitHub

Get the beta CLI: notifai update --channel beta

· Beta release

Notifai update

  • CLI 11.6.3-beta.2 · npm

What changed

  • Avoid question failures from unnecessary permission changes in restricted environments.
  • Question errors now explain when Notifai needs filesystem or sandbox access.
Full CLI changelog for 11.6.3-beta.2

Bug Fixes

  • Avoid redundant permission changes when private state already has the required modes, including in sandboxes that deny chmod.
  • Report Project Enablement write failures as actionable question-command errors before registration.

View the CLI changelog on GitHub

Get the beta CLI: notifai update --channel beta

· Beta release

Notifai update

  • iPhone 1.0 · TestFlight · build 62
  • Android 0.1.0 · Firebase App Distribution · build 37
  • Android 0.1.0 · Google Play Alpha · build 38
  • Android 0.1.0 · public direct download · build 39

What changed

  • Read earlier Agent Session history without losing your place.
  • Home previews the latest activity, including your replies and Session Notes, and lets you hide read finished sessions after a delay.
  • Session Notes expand to the space available above the keyboard, making longer drafts easier to edit.

Update the iPhone app: Open TestFlight.

Update Android via Firebase App Distribution: Use your Firebase App Distribution invitation.

Update Android via Google Play Alpha: Update in Google Play through your Alpha tester access.

Android direct download: Get the latest Android APK. View this release.

· CLI beta on npm

CLI 11.6.2-beta.1

What changed

  • Codex delivery checks now verify the current conversation turn and explain how to recover stale hooks without restarting the agent.
  • Pending notes and answers are reported honestly when delivery is blocked, instead of appearing as an empty inbox.
Full generated changelog

Sources for the summary

  1. Note 1: commit 76928a1
  2. Note 2: commit 76928a1

Bug Fixes

  • cli: verify current root delivery callbacks and report blocked input (#235) (76928a1)

View the CLI changelog on GitHub

Get the beta CLI: notifai update --channel beta

· Beta release

Notifai update

  • CLI 11.6.1-beta.6 · npm

What changed

  • Codex activity now follows its native turn lifecycle, reducing stale Working and Idle states.
  • CLI updates activate existing session attendants and verify the implementation they are running.
  • Questions submit immediately, and Codex notes and answers keep their latest content and correct owner through queued delivery.
Generated changes since 11.6.1-beta.5

Bug Fixes

  • Reconcile Codex Working and Idle state with the exact native turn lifecycle.
  • Activate existing session attendants during update recovery and verify their loaded implementation.
  • Preserve parent notes and pending delivery while child agents work, with queued fallback delivery.

Dependencies

  • Pin the verified @raidiant/notifai-protocol artifact at 8.1.4-beta.2.

View the CLI changelog on GitHub

Get the beta CLI: notifai update --channel beta

Earlier betas for 11.6.1 (3)

· Beta release

Notifai update

  • CLI 11.6.1-beta.5 · npm

What changed

  • Codex child agents no longer consume parent notes or leave the parent falsely marked as working.
  • Pending Codex notes keep a queued delivery path even when another tool callback never arrives.
Generated changes since 11.6.1-beta.3

Bug Fixes

  • Keep child callbacks from consuming parent input or changing parent activity.
  • Wake pending input even when activity suggests a later tool callback, retaining claim and duplicate-delivery protection.

View the CLI changelog on GitHub

Get the beta CLI: notifai update --channel beta

· Beta release

Notifai update

  • CLI 11.6.1-beta.3 · npm

What changed

  • Questions start sending immediately while agents continue independent work.
  • Pending notes and replies are collected together at supported Codex and Claude input boundaries, with corrected session resolution and fewer stale duplicate replies.
  • Automatic Codex continuations can receive notes at trusted tool callbacks without waiting for another human prompt.
  • Note retries retain their accepted order, with clearer local delivery diagnostics.
Generated changes since 11.6.1-beta.2

Bug Fixes

  • Resolve queued receive commands from the exact active harness session instead of a filesystem key.

View the CLI changelog on GitHub

Get the beta CLI: notifai update --channel beta

· Beta release

Notifai update

  • CLI 11.6.1-beta.2 · npm

What changed

  • Questions start sending immediately while agents continue independent work.
  • Pending notes and replies are collected together at supported Codex and Claude input boundaries, reducing stale duplicate replies.
  • Automatic Codex continuations can receive notes at trusted tool callbacks without waiting for another human prompt.
  • Note retries retain their accepted order, with clearer local delivery diagnostics.
Full CLI changelog for 11.6.1-beta.2

Bug Fixes

  • Start question submission immediately so agents can continue independent work; preserve answer observation across concurrent questions and uncertain network responses.

  • Preserve accepted note order across release and retry, and wake the resident Claude delivery process promptly when answers become available.

  • Deliver pending notes and answers together at supported Codex and Claude input boundaries, and queue content-free wake prompts to avoid stale answer copies.

  • Observe automatic Codex turns at trusted tool callbacks so busy sessions can receive pending input without waiting for another human prompt.

  • Record delivery stages, batch sizes and oldest pending note age for clearer local diagnostics.

  • Accept repeated successful CI evidence for one release commit while requiring all checks from one complete run.

View the CLI changelog on GitHub

Get the beta CLI: notifai update --channel beta

· Beta release

Notifai update

  • CLI 11.6.0-beta.4 · npm

What changed

  • CLI updates refresh the existing skill and owned hooks together, while preserving healthy Codex approvals and active question routing.
  • Agents receive a quiet local warning when installation drift affects note delivery or question routing, without repeated interruptions.
  • Native hook approval and runtime activation remain explicit; updating preserves pending questions, answers and acknowledgements.
  • Known Hermes 0.21.5 issue: background review can change its session identity and block later questions. Disable background review while testing this integration.
Generated changes since 11.6.0-beta.3

Bug Fixes

  • cli: preserve Codex approval identities during missing-hook repair, including empty groups and foreign handlers (#221) (e085037).

This beta replaces beta.3's missing-hook repair, which could reorder otherwise healthy Codex handlers and invalidate their approval. Existing hooks now refresh in place; ambiguous duplicate or retired Codex slots require an explicit migration. The protocol remains 8.1.2. Pending work, native trust and existing matcher restrictions remain User-owned. This beta also includes beta.2's harness and session-naming improvements.

View the CLI changelog on GitHub

Get the beta CLI: notifai update --channel beta

Earlier betas for 11.6.0 (2)

· Beta release

Notifai update

  • CLI 11.6.0-beta.3 · npm

What changed

  • CLI updates refresh the existing skill and owned hooks together, with a resumable check when integration still needs attention.
  • Agents receive a quiet local warning when installation drift affects note delivery or question routing, without repeated interruptions.
  • Known issue: repairing missing Codex hooks can change existing approvals; beta.4 contains the corrected repair.
  • Known Hermes 0.21.5 issue: background review can change its session identity and block later questions. Disable background review while testing this integration.
Generated changes since 11.6.0-beta.2

Bug Fixes

  • cli: migrate owned integration during updates and detect local drift without repeated notices (#219) (fea78df).
  • cli: isolate healthy lifecycle fixtures and verify one-time native-approval diagnostics (#220) (51ef7c9).

This beta includes the harness and session-naming improvements from beta.2. The protocol remains 8.1.2. Updates preserve pending questions, answers, acknowledgements and native approval; native activation is reported separately from package installation.

View the CLI changelog on GitHub

Get the beta CLI: notifai update --channel beta

· Beta release

Notifai update

  • CLI 11.6.0-beta.2 · npm

What changed

  • Hermes classic CLI can receive Session Notes, answer edits and question answers in the same live session, including while busy.
  • OpenClaw on macOS can receive Session Notes and answer edits through its local Gateway, with protection against delivery to a reset session.
  • Agents get clearer guidance to rename a session when its job changes, and the CLI explains when a label flag leaves an existing name unchanged.
  • Known Hermes 0.21.5 issue: background review can change its session identity and block later questions. Disable background review while testing this integration.
Full CLI changelog for 11.6.0-beta.2

Features

  • cli: deliver Session Notes, answer edits and attended question answers in Hermes local classic CLI sessions (#213).
  • cli: deliver OpenClaw Session Notes and answer edits through macOS Gateway followups, with native reset fencing and one-time private context (#213).

Bug Fixes

  • cli: prompt exact-session renaming when the job changes and explain ignored label flags (#217).
  • cli: preserve note acknowledgement ownership and journal replay protection across OpenClaw resets and restarts (#213).

View the CLI changelog on GitHub

Get the beta CLI: notifai update --channel beta

· Beta release

Notifai update

  • iPhone 1.0 · TestFlight · build 61
  • Android 0.1.0 · Firebase App Distribution · build 35

What changed

  • See which Agent Sessions are running and leave a Session Note to steer a supported agent from either Companion App.
  • Edit a sent answer, and use Send Delay to keep editing before a response is sent.
  • Missed requests return to history, and gallery images can be saved to your phone.
  • Known iPhone beta issues: some Sessions may appear unread after viewing, and the app may occasionally close when you return to it.

Update the iPhone app: Open TestFlight.

Update the Android app: Use your Firebase App Distribution invitation.

· CLI beta on npm

CLI 11.4.0-beta.2

What changed

  • Questions routed through Notifai no longer show a second answer form, and a Codex question stays available for your answer after its session stops.
  • Beta testers can update to the newest beta without accidentally installing an older stable release.
Full generated changelog

Sources for the summary

  1. Note 1: commit fa66090 · commit a696e04
  2. Note 2: commit 54ae1ef · commit 28d2229

Features

Bug Fixes

  • cli: avoid duplicate question forms for routed decisions (#194) (fa66090)
  • cli: keep Codex question owner alive after Stop (#195) (a696e04)
  • cli: order release versions by full SemVer precedence (#196) (28d2229)
  • release: isolate secret-scanner controls from Git hooks and refresh the agent guidance review (#198) (b13c66d)

View the CLI changelog on GitHub

Get the beta CLI: notifai update --channel beta

· Beta release

Notifai update

  • iPhone 1.0 · TestFlight · build 48
  • Android 0.1.0 · Firebase App Distribution · build 29
  • Android 0.1.0 · public direct download · build 28

What changed

  • Custom sounds load more reliably, and the iPhone app stays responsive while checking saved sounds.

Update the iPhone app: Open TestFlight.

Update Android via Firebase App Distribution: Use your Firebase App Distribution invitation.

Android direct download: Get the latest Android APK. View this release.