Notifications

Foxl can tell you when long-running work finishes, so you do not have to sit and watch it. Every notification is opt-out per category, and nothing is sent unless the work you started actually completed.

Where to control them앵커 링크 복사

Settings > Notifications, on every platform. The pane is organised by where a notification arrives:

• This device - in the desktop app, its own toasts, one switch per event type; in a browser, only the Browser notifications switch below. These switches decide this computer's banners and its bell together: a type switched off neither pops up nor adds a row to the bell. Quiet Feed items, and a reply Foxl could not send back to a channel, are listed regardless, and entries already in the list stay until you clear them. What reaches your phone is decided by the phone categories below. Only when in background is on by default, so nothing pops up over the window you are looking at; the bell still records it. On a new desktop install the two Task Completed switches (under Schedules and Agent) start off, so Foxl does not tell you when a schedule or an agent finishes; it still tells you when one fails, when a device connects and when something needs your answer. A computer that already used Foxl keeps them as they were. Reply ready, under Chat (on by default), shows a banner titled with the chat's name, saying "reply ready", when a chat reply that took 30 seconds or more finishes, or stops with an error, while the Foxl window is in the background; clicking it opens that chat. It makes no sound, a shorter reply shows none, it never shows while you are looking at the chat (in the main window, in a chat popped out into its own window, or in Quick Chat with its window in front), and it adds no row to the bell. A chat that hands work to subagents shows one banner for the final answer, not one for the hand-off, timed from your message. A reply to a message you sent from your phone or app.foxl.ai shows none on the computer.
• Browser notifications - on app.foxl.ai and code.foxl.ai, off until you press Turn on (in This device, and in Foxl Code's Settings > Notifications); your browser asks for permission then, never before. A Foxl Code task that finishes or fails, or a run that needs your answer, shows a notification while you are working in another window; on app.foxl.ai, so does an agent run or a schedule on your desktop that finishes - unless the Foxl desktop app is running on the same computer, which shows its own notification instead (the run is still listed in the tab). Foxl recognizes the same computer by its IPv6 address. With the desktop app open on a Mac, the browser also skips its notification while you are at that Mac and the Mac shows its own, on any network and in any browser signed in to your account; once you have been away from the Mac for a minute or more, it is locked or asleep, or that kind of notification is off in the desktop app's Settings > Notifications, the browser notifies you. Over IPv4, which a whole home or office network shares, a Windows or Linux desktop's notification can come with the browser's. Foxl Code updates arrive only while a Foxl tab is showing, so a minimized window or a tab behind another tab catches up when you return to it. Notifications with every Foxl tab closed are not available yet.
• Phone push - the categories below. They are stored with your account, so you can turn a phone category off from your desktop, and they apply to every phone signed in as you. They also decide the phone app's own bell: with Chat replies off (or Scheduled tasks, for a schedule), a run finishing on your desktop is not listed there either. The pushes Foxl sends for your desktop's notifications (a schedule's result, a finished agent run) are paced: up to 60 at once, then one every 20 seconds, which is well above what real schedules and agent runs produce. Past that pace a push is skipped; the notification still reaches app.foxl.ai and an open app. A desktop that reaches its daily message limit with the relay stops reaching the phone, notifications included, until 00:00 UTC.
• Email - two categories and a blanket unsubscribe, see Email.
• Test - fires a real notification through the real pipeline, so you can see where it lands.

On a phone the pane also shows the operating system's permission state and a link into the system settings when permission has been denied there (no in-app toggle can grant that for you). Push needs two things to be true: the operating system has granted Foxl permission, and the category is enabled. If you never see a notification, check the permission state first. If you declined the prompt and later switched notifications on for Foxl in iOS Settings, Foxl re-registers the next time you come back to it - no relaunch needed.

The categories앵커 링크 복사

Channel messages and Huddle invites belong to team workspaces: they ring only for a workspace you are in.

Everything useful defaults to on because it is low-volume and follows an action you took. Only marketing and issues the loop files for itself are opt-in: neither is sent unless you explicitly enable it. The issues are opt-in because the loop has already decided what to work on and asks nothing of you; you still hear from Code tasks when that work needs you.

A message that reaches your agent through a channel bot (Telegram, Slack, iMessage and the others) is not one of these: it shows as a desktop notification and in the bell on connected devices, and does not push to your phone. In the desktop app, Channel Messages under This device has a switch for Telegram, Slack and Signal each, and one Other channels switch for Discord, iMessage and the rest.

Where each one opens앵커 링크 복사

A notification that leads nowhere is worse than no notification, so every push the server can send is checked against both doors - the banner from the operating system and the row in the bell - and one that leads nowhere fails the build rather than shipping.

This holds whether the app was open, in the background, or closed, and the rows in the bell lead to the same places as the banners.

The desktop app's own banners open the same places, and three more: a Feed item opens the Heartbeat run that wrote it (an item from before that update opens the Notifications page), a message that reached your agent through Slack, Telegram or another channel opens that thread in Channels, and "Device connected" opens Settings > Connect > Mobile/Web.

The badge, the bell and the banner agree앵커 링크 복사

• The number on the app icon is exactly the bell's count. They used to be computed differently, so a phone could show three on the home screen and one on the bell for the same list. Everything the badge counts is now reachable, so it can always get to zero.
• The count advances per notification. Each push used to carry a hardcoded badge of 1, so three replies arriving while the app was closed still read as 1.
• Product updates and promotions do not touch it at all. They add nothing to your inbox, and a badge on them used to reset a genuine count of five down to 1.
• Reading in the app clears the lock screen. Rows you read, archive, swipe away or clear have their banners removed. Unread items are left alone in both places.
• A follow-up replaces the one before it. Updates about the same conversation, task, question, note or call collapse onto the previous banner, so a task that became ready to merge and then merged does not leave two banners saying different things. Separate things stay separate.
• Signing out on a phone clears its bell and its banners, and a reply typed from a notification is never sent under the next account on a shared phone.
• Opening the app no longer resets the count, and a second phone on the same account no longer wipes the first one's number - the badge is one number per account.
• Read all is a word, not an icon. In the notification panel it sits at the top right next to the close button; in the iPhone app it is a button beside the All / Unread switch (a double check mark in a language whose label does not fit there), and the ... menu keeps Clear all.
• Notifications come in the app's language - the desktop app's bell and banners, and app.foxl.ai's bell and browser notifications, for finished and failed agent runs and schedules, a paused schedule and a channel reply that could not be sent. A lock-screen push on a phone is in English, and an error message inside a notification is shown as the service wrote it.

The macOS dock badge is deliberately different앵커 링크 복사

On the desktop, the dock badge keeps counting unread conversations alongside notifications. A reply that lands in a conversation you are not looking at files no notification of its own there, so the badge matches the sidebar's Chat row, which counts the same thing.

Chat replies앵커 링크 복사

A reply can take a while on a hard question, and if you leave the app before it lands there is nothing on screen to tell you it did. This fires only when you were away when the response completed - if you watched it stream, you already know.

Tapping the notification opens that conversation.

The agents a chat starts along the way to its answer also notify here when they finish or fail, quietly: no sound and no banner, and they share one entry for that conversation in your notification list, so a question split across five agents does not buzz five times.

Notes transcripts앵커 링크 복사

Transcribing an imported recording takes roughly as long as the audio, so the natural thing is to start it and put the phone down. This category covers a finished transcript, and also the AI results that follow it - the summary and the coaching report, which are the slowest steps because they read the whole transcript. Tapping it opens the note that finished.

A summary you watched appear on screen does not notify you; only one that landed while you were elsewhere.

Because Notes does its transcription work on the device rather than on our servers, the app itself reports completion. If you force-quit Foxl mid-import, the import stops with it and no notification is sent. Which transcription destination you use - your own AWS account, On device, or your own Deepgram, AssemblyAI, OpenAI, ElevenLabs, Gemini or OpenRouter key - does not change this; the app reports completion in every case.

Meeting reminders앵커 링크 복사

With a calendar connected in Settings > Notes > Calendar, the desktop app shows a banner 5 minutes before a meeting with at least one other person, for example "Design review starts in 5 min". On macOS it has a Record button that opens Notes and starts recording that meeting; on Windows and Linux, clicking it opens Notes. The switch and the timing (Remind me 1, 5 or 15 minutes before) are in the calendar settings, and the banner also follows This device: with its notifications turned off there is no reminder, and Play a sound with notifications decides whether it makes a sound. It is never a phone push, and nothing records until you press Record. See Calendar meetings.

Code tasks앵커 링크 복사

A Foxl Code task runs on its own and can take minutes. This fires when the task reaches a state that wants your attention: a pull request ready for review, a merge, or a failure. It also fires when the task's pull request fails its checks, or a reviewer requests changes or approves it and it is waiting for your merge - including after the agent has finished, which is when CI and reviews usually report.

A tool waiting for your approval앵커 링크 복사

On the desktop, once you have turned auto-approve off (see Security), a tool that asks first waits for your answer. If the Foxl window is in the background, a notification says so. It shows the whole request (the command and its folder, or the tool and its arguments) when it fits, and otherwise asks you to open Foxl to read it. Clicking it opens Foxl, where the request has Allow and Deny.

On a Mac the notification also has Deny, which turns that request down without bringing the window forward. If the request has already timed out or been answered in the app, Deny does nothing. There is no Allow on the notification: Foxl cannot make a notification button require an unlocked Mac, so allowing is done in a Foxl window. On Windows and Linux the notification has no buttons.

While your phone or app.foxl.ai is connected to this computer, the same request also shows there, in the chat that asked or as a card at the top right, and can be answered from there: see Answering a prompt from your phone or the web. On a phone (the iPhone and Android apps and a phone's browser) the request is a card that shows exactly what Foxl is about to do - for an email or a channel message, who it goes to (Cc and Bcc included), the subject and the words - with Send or Approve, Not now (which declines it) and Always allow under them.

Some requests ask even with auto-approve on, and offer no Always allow: a message, mail or typed text that carries a card number, a Korean resident registration number or a US Social Security number (the prompt names a card or an SSN by its last four digits only, and a resident registration number by its kind), and a click in the browser that can pay or book. A scheduled or channel run that reaches one sends or clicks nothing when no Foxl window is open to ask.

Promotions and tips앵커 링크 복사

The only category that is off unless you turn it on, and the only one not caused by something you did. If you enable it, you will hear from us at most once every 30 days - that limit is enforced on our side, not a promise about intent.

What you receive depends on which parts of Foxl you use and how long you have been here, so the message is at least relevant. That grouping is based on counts and dates - your tier, when you signed up, when you were last active, whether you have used Notes or Code. It never involves the contents of your messages, transcripts or files.

You will not hear from us in your first week, whatever your settings say.

Email앵커 링크 복사

Two categories, stored with your account and editable in the same pane (or from the link in any marketing email, signed out):

The Unsubscribe link at the bottom of a product-update or tips email opens a page that asks you to confirm, and its button turns off all Foxl email at once (your mail app's own unsubscribe button does the same in one click). It stays that way, whatever the switches say, until you turn email back on. Sign-in links, receipts, payment problems and the usage notices at 80% and 100% of a credit allowance are part of the service and are always sent.

Requirements앵커 링크 복사

Your phone registers itself with Foxl once, the first time you run the app and grant permission. That registration is tied to your account, so notifications follow you across devices signed in to the same account, and signing out on a device stops that device receiving them. Logging a phone out from your device list, or signing out your other devices when you change your password, stops that phone's notifications too, once it has signed in to Foxl since v0.7.33; a phone that has stayed signed in since before then is stopped by Sign out everywhere. Signing back in on the phone turns its notifications back on.

Privacy앵커 링크 복사

Notification text contains only what you need to recognise the event - a conversation title, a note name, a task title. The body of a message, the contents of a transcript, and any file content are never included in a notification payload.