Skip to content

Phone & browser notifications (Web Push)

StockClaw can send system-level notifications to your phone and to any browser you've signed in from, without you having the tab open. They carry the same alerts as your Telegram digest, on the same schedule. Click a notification and it opens the dashboard, on the specific signal when the notification is about one signal.

You don't need Telegram for this. Push works on its own; if you never link Telegram, the defaults below apply.

What you receive

Phone and browser notifications mirror the Telegram digest exactly. Whatever you set under Settings → Alert tiers & frequency applies to both:

  • Tiers. FLASH and ALERT by default. NOTE and FYI only if you switch them on.
  • Frequency. Signals are batched at your Push frequency (every 30 minutes at the shortest, up to once a day). This includes FLASH: it arrives with your next digest, not instantly.
  • Quiet hours. If you turn on Settings → Quiet hours, nothing is sent to your phone or Telegram between the start and end time in your time zone, FLASH included. Nothing is lost: what was held goes out together with your next digest after quiet hours end. The time zone is taken from your device the first time you open Settings and can be changed there. Market Wire alerts that come in during quiet hours are held as well and sent when quiet hours end, up to the newest 10.
  • Watchlist filter. Only signals whose impact on one of your watched tickers is at least 0.60.
  • Free version. FLASH and ALERT only, at most every 30 minutes, no quiet hours; the tier, frequency and quiet-hours controls are shown locked. See How much does this cost?.
  • Language. Your app language, the same one the app shows on every device (Settings → Display). Chinese gets the Chinese summary; English gets English only, with a short "details in the app" line when a signal has no English summary; Japanese and Korean get translated titles and buttons with the English summary.

Each digest sends one notification per tier rather than one per signal, for example FLASH · NVDA, AAPL or 3 ALERT signals · NVDA, TSLA, AMD. A notification about a single signal deep-links to that signal; one covering several signals opens the dashboard.

Market Wire. Market-wide events with impact of 0.80 or more also push, to everyone who has notifications on and the FLASH tier enabled.

Notifications describe market events the pipeline has already scored. They are not investment advice.

Where it works

  • Desktop: macOS Notification Center, Windows Action Center, Linux DE notifications. FLASH banners stay sticky until dismissed; ALERT fades after the OS default.
  • Android: lockscreen banner + persistent entry in the notification shade.
  • iOS Safari: only after you install StockClaw as a PWA — "Add to Home Screen" from the Share menu, iOS 16.4 or later. Standard Safari tabs do not support Web Push, per Apple's rules.
  • Android app (Google Play, currently in testing): enabling works the same way as in the browser, and Android shows its own notification permission prompt.

Clicking the banner:

  • If you already have a StockClaw tab open, it focuses that tab and navigates it to the signal (or to the dashboard for a multi-signal notification).
  • Otherwise opens a new tab there.

For a single-signal notification, the dashboard scrolls to that signal card and flashes the accent border for ~2 seconds so it's easy to find.

Enable

There are two ways in.

From the dashboard. Signed-in users see a card asking Get alerts on this phone? Tap Turn on, then allow the permission prompt that follows (on Android 13 and later this is the system prompt). Not now hides the card for 14 days.

From Settings. Settings → Phone & browser notifications → Enable. The flow:

  1. Browser (or Android) shows its native permission prompt — choose Allow.
  2. StockClaw registers this device's push endpoint with the backend.
  3. Button flips to Disable.

Each browser you sign in from subscribes separately — your phone and your laptop can both receive, or just one of them, independently. Unsubscribing from one device does not affect the other.

Send test

Once a device is subscribed, Settings → Phone & browser notifications → Send test sends a test notification to your devices, so you can check this one actually receives it. The button has a 30-second cooldown.

Disable / revoke

  • Inside StockClaw: Settings → Phone & browser notifications → Disable. One click. Unsubscribes that browser and tells the backend to prune the row.
  • Browser-wide: site permissions in Chrome (or equivalent) → revoke notifications for StockClaw. Server-side subscription rows get pruned on next delivery attempt (404/410 from the push service).

iOS PWA install

To receive web push on iPhone / iPad:

  1. Open StockClaw in Safari (Chrome on iOS doesn't count — it uses WebKit but has fewer PWA features).
  2. Hit the Share icon → Add to Home Screen.
  3. Launch StockClaw from the home-screen icon (not from Safari). This starts the app in standalone PWA mode.
  4. Go to Settings → Phone & browser notifications → Enable. iOS will prompt for permission.
  5. Close the app. Notifications now land on the lock screen.

Privacy

Payload contents are encrypted end-to-end between our backend and your browser using VAPID + the subscription's own P-256 keys — intermediate push relays (Apple, Google FCM, Mozilla autopush) cannot read the payload, only route it. We store the subscription (endpoint URL, public keys, user agent) on your push_subscriptions row with the same row-level security as every other table. Nobody else's browser can receive your signals.

Troubleshooting

"Enable" button is greyed out and reads "Unsupported":

  • Your browser doesn't have a PushManager (very old Safari, older Firefox). Upgrade the browser.

"Enable" button reads "Blocked in browser":

  • You previously denied the permission prompt, and the browser remembers. Click the URL-bar padlock icon → reset notifications to "Ask", then reload.

Subscribed but no notifications arriving:

  • Celery workers must be running (pipeline writes + delivery happen there).
  • Check your tiers and frequency under Settings → Alert tiers & frequency. Notifications follow the same digest, so with a 4-hour frequency nothing arrives in between, and NOTE/FYI only push if you switched them on. Signals below 0.60 impact on your watched tickers are dashboard-only.
  • Press Send test. If the test arrives, delivery works and there simply hasn't been a qualifying signal since your last digest.
  • Open StockClaw once on that device. The app re-registers the browser's current subscription with the backend on every launch, and Settings shows Disable only when the backend actually holds this device's subscription. Browsers (iOS home-screen apps especially) rotate subscriptions from time to time; before 2026-09 a rotated or server-pruned subscription could leave the button reading Disable while nothing was delivered. If Settings reads Enable on a device you thought was subscribed, click it to re-register.
  • Try the Console smoke test from the sign-in page documentation to send yourself a local notification and confirm the service worker is alive.

One notification for several signals:

  • Expected. Each digest sends one notification per tier (3 ALERT signals · NVDA, TSLA, AMD), the same grouping Telegram uses. Tap it to open the dashboard and see every signal in the batch.