Notifications in Aikeedo: Know When the AI Is Done, Even With the App Closed

A video takes minutes to render. A long reply with web searches and a Canvas document takes a while too. And a scheduled task runs at 7:30 in the morning, when nobody is looking. In each case, the user's question is the same: is it done yet?

Until now, the only way to find out was to keep the tab open and check. v5.2 adds notifications: a bell inside the app, and browser alerts that arrive even when the app is closed.

The Bell

Every signed-in user now has a bell beside the sidebar's other actions, and in the header on mobile. When something new arrives, it shows a dot — a dot, not a count, because a number that keeps climbing turns into noise.

Open it with a click or Ctrl/⌘ + Shift + B. The list loads as you scroll, and Mark all as read clears it. Each notification links straight to the item.

Users are notified when:

• A reply is ready — or failed
• A chat needs input — a clarifying question or a tool that needs approval
• Media is ready — an image, video, speech, transcription or isolated voice — or its generation failed
• A scheduled task has run — finished or failed

Notifications come only from work that was still running, so things that finish instantly do not ring the bell. Anything created in private mode never does.

Leave the Page, Keep the Reply

Notifications only help if the work keeps going while the user is away. In v5.2, chat replies keep running on the server after the user leaves the page, just as image and video generations already did.

While something is still running, a small notice tells the user they can leave the page and offers Notify me. One click turns on notifications for that kind of work, and asks the browser for permission to show alerts. Come back later, and the result is under the bell.

Browser Alerts With the App Closed

Inside the app, the bell is enough. Outside it, Aikeedo uses browser alerts — the same kind of notification a messaging app shows.

They are built in. Aikeedo sends them with Web Push, the standard every major browser supports, and a service worker that shows the alert even when every tab of the app is closed. There is no third-party push service to sign up for, and no keys to create — Aikeedo generates its own the first time a browser asks. Alerts carry your app icon from the PWA settings, and clicking one opens the item.

A few things worth knowing:

• The app tab wins. If the app is open and visible, the browser does not pop up an alert. The bell picks it up instead.
• Up to ten browsers per user. Signing out removes that browser.
• HTTPS is required. Browsers allow push only on secure sites.

If you already use the OneSignal integration, it keeps working separately. Built-in alerts do not need it.

Users Choose What They Hear About

Under Settings → General → Notifications, each user decides what reaches them:

• Response completions
• Media generation completions
• Scheduled tasks — shown when the feature is on
• Requests for input

Switching one off means that kind of event creates no notification at all, under the bell or as an alert. A Browser alerts row shows whether this browser allows them, with a button to allow them if it has not been asked yet.

The Operator Perspective

Notifications work out of the box. A new page under Settings → Notifications lets you adjust two things:

• Browser alerts. Enabled by default. Switch them off and the app stops asking for the browser permission and sending alerts. The bell keeps working.
• Retention. Read notifications are deleted after 30 days, and every notification after 90 days, by default. Both can be set from 1 to 3,650 days. Old notifications are cleared once a day.

Alerts are sent from the new background queue, so keep cron running every minute. A background worker sends them a little sooner but is optional.

Plugins can add their own notification types, so the bell grows with your platform.

Getting Started

Update to v5.2 and make sure your site is served over HTTPS and cron is running. That is all. Your users see the bell right away and can allow browser alerts from it or from their settings.

The notifications documentation has the details, the feature page has the overview, and the v5.2 release post covers everything else that is new.

Try the live demo to see it in action, or head to our pricing page if you are ready to get started.