AI alarm clock: what changes when your alarm watches the internet

A short history of the alarm clock

For most of its history the alarm clock solved one problem: ring at a time you chose the night before.

When	What happened	Worth knowing
1787	Levi Hutchins of Concord, New Hampshire, builds a clock that rings at 4 a.m. to wake him	It only ever rang at 4 a.m., and he never patented it. It is called the first American alarm clock, not the world's first
1847	French clockmaker Antoine Redier is credited with the first patent for an adjustable mechanical alarm clock	Now the time could be set
1876	US Patent 183,725 goes to Seth E. Thomas for a small back-winding bedside alarm clock	The patent covered the clock's case, not the alarm itself, despite what many sites say
Late 1940s	Clock radios go on sale	Popular Science reported 2.3 million sold in 1958, by 25 manufacturers
2009	Sleep Cycle launches, which the company calls the first smart alarm clock app	It used the iPhone's motion sensor to wake people in a lighter sleep phase within a window
Mid 2010s	An Edison Research survey of 1,550 Americans aged 18 to 54 finds about half use an alarm, and half of those wake to a phone	Only 15% of alarm users woke to the radio

Each era changed what wakes you: a bell, then a radio station you chose, then the phone, which put the alarm in the same device as your messages and feeds, then a sleep tracker that picks a gentler minute inside a window. None changed the question the alarm answers. Every one assumes the thing you need to be up for has a time, and that you already know it.

What changes when an alarm watches the internet

A lot of what people want to be up for has no time attached. A streamer goes live when they go live. A token crosses your number at 3:40 in the morning. A wallet you follow buys. Your server falls over. A clock-only alarm cannot help, so people fill the gap by checking: refreshing a profile, leaving a chart open, sleeping with notifications on for an app that sends forty other things.

LFG Alarm adds a second kind of trigger. An alarm can be set off by a time, or by a moment:

Alarm type	It rings when	How Rocco knows
Time	A clock time comes, once or on chosen days	The phone's own clock, no signal needed
Event	An event you pasted from a Luma or Partiful link is about to start	Rocco reads the start time from the invite page
Post	An account on X posts something that means what you described, or a Twitch or YouTube channel goes live or posts a video	Rocco reads each new post and rings only for the ones that match your words
Price	A token reaches a price, or moves by a multiple or a percent	A number and a comparison
Trades	A wallet, a FOMO trader or a GMGN KOL makes a buy or sell over your floor	Public trades, with no wallet connected and nothing signed
Anything	Any script, bot, Zapier, IFTTT or site monitor calls the alarm's private link	A web request to that link

Calling all of this AI would oversell it. A price alarm is a number and a comparison; an anything alarm is a link that rings when it is called. The part that earns the word AI is reading. A post alarm on X takes a rule written in your own words, such as "announces a launch date" or "posts a contract address for a new token", and Rocco decides whether each new post means that. Keyword alerts cannot tell "we launch Friday" from "we are not launching Friday". That reading step is what makes a post alarm quiet enough to leave on overnight.

Three scenes where this matters:

• The drop. Ji-woo in London is waiting on a Seoul release the label has only dated "this week". A post alarm on the label's X account, with the rule "announces the exact release time", rings her, and her fan chat rides the same alarm. See KST to your time.
• The 3 a.m. trade. Priya follows a Solana wallet and only cares about buys over $5,000. A trades alarm with a $5k floor stays quiet for small trades and rings when it matters.
• The side project. Sam runs a small app on a cheap server. His uptime monitor calls an anything alarm when the site stops answering, with a 10 minute cooldown so a flapping server rings him once.

How hard each one rings depends on the phone. Time and event alarms are real alarms on both: on iPhone they use Apple's AlarmKit and ring through silent mode and Focus, and on Android they take over the screen. Post, price, trades and anything alarms need a connection, because the server notices the moment and tells the phone. On Android they ring full screen, even on Do Not Disturb. On iPhone they arrive as a time-sensitive alert with the alarm's own sound, which respects the silent switch, so keep the ringer on.

Alerts are a category, and it has two halves

Alarm clocks wake people; alerts tell people something happened. The most developed version of "make sure a person notices" is not consumer software at all. It is incident management.

The business half. On-call tools are built around one idea: a page is not done until someone acknowledges it. In PagerDuty, an escalation policy notifies the first level at once; if nobody acknowledges before the timeout, the incident moves to the next level, and acknowledging stops the escalation. incident.io's escalation paths work the same way, setting who is paged at each level and how long to wait, and can be triggered from an alert or from Slack. And they are meant to fire rarely. Google's Site Reliability Engineering book says one incident takes about six hours to handle properly, so an on-call engineer should face at most two per 12-hour shift, and the likely median is zero.

The personal half. Nobody gives you an escalation policy for your own life. There is no rota, no second level, no manager watching the timeout. The question is simpler and harder: what do I actually want to be interrupted for? For most people the honest list is short. A flight. A friend's party. One account's post. One price. One wallet.

A watching alarm borrows the useful part of the on-call model, a rare, loud signal that has to be answered, for that short personal list. LFG Alarm is not an on-call tool: it has no escalation policies or schedules. Its version of acknowledging is tapping I'm up, and its version of a second level is the friends on the same alarm, who can see on the wake board whether you did.

Why notifications stopped working

A separate alarm is worth having because ordinary notifications have stopped carrying weight. In a 2018 study of 278 smartphone users, the median was 56 notifications a day. Airship's 2026 benchmarks put direct push open rates anywhere from under 1% in the weakest app categories to about 21% at the 90th percentile in the best. And in a lab experiment with 166 students, merely receiving a notification, without answering it, hurt performance on an attention task about as much as using the phone. When everything buzzes, a buzz means nothing. The longer version, with hospital alarm data and what follows from it, is in notification fatigue.

Why friends make waking up stick

Snoozing is the normal way people wake up, not a failing. In about 3 million sleep sessions from 21,222 Sleep Cycle users, about 56% ended with a snooze. In a survey of 1,732 adults, 69% said they use snooze or several alarms at least sometimes, and the same research found that a 30-minute snooze did not harm habitual snoozers' sleep. Being groggy in the first minutes is normal too: sleep inertia is worst when woken from deep sleep and, without major sleep loss, rarely lasts more than about 30 minutes.

So the useful question is how to make getting up more likely on the mornings it counts. The research on doing things with other people is fairly consistent:

• In a randomised trial of 166 adults in a weight-loss programme, 95% of those who joined with friends and had social-support training completed treatment, against 76% of those who joined alone. Two thirds of the friends group kept the weight off fully over the following months, against about a quarter of those who joined alone.
• In an exercise study of 153 students, people with a virtually present partner held plank exercises significantly longer than people exercising alone, a pattern researchers call the Kohler effect.
• A meta-analysis of 241 studies found that the presence of others slightly improves performance on simple tasks. Getting out of bed is about as simple as tasks get.
• stickK's own data suggests commitments with a referee succeed far more often than commitments with none, though motivated people are also the ones who choose a referee.

LFG Alarm applies this in a light way. Share a time alarm and everyone who joined is rung at the same moment, or each at their own local time for a routine across time zones. The wake board then shows who got up first, who snoozed most and who slept in. Snoozing stays allowed: you pick 5 to 60 minutes and 3, 10 or forever for how many times, and a chaos level of mild, medium or feral sets how hard Rocco roasts a snooze. The pressure comes from being seen, not from a lock.

Setting alarms from your AI agent

The other meaning of "AI alarm clock" is an alarm your AI assistant can set for you. LFG Alarm has an MCP server, so Claude, ChatGPT, Grok, Gemini and other AI apps that can add a remote connector with sign-in can work with your alarms once you connect it. See connect LFG Alarm to your AI app.

What works through an AI agent today: time, price, post, event and anything alarms; listing, changing and deleting them; adding friends by username or anyone by email; choosing a wallpaper; and getting a one-time link to add your own picture, video, song or voice. Wallet and trader alarms are made in the app for now.

Where a watching alarm is the wrong tool

• Work incidents. If a team has to respond, with handovers and escalation, use an on-call tool.
• Sleep insight. If what you want is sleep stages and a light-sleep wake window, a sleep tracker such as Sleep Cycle or Sleep as Android is built for that. See the best alarm clock apps.
• Emergencies. LFG Alarm is not an emergency service.
• Your laptop alone. A laptop rings only while an lfg.gm tab is open and the laptop is awake and online, for up to ten minutes; phone browsers never ring. The app on the phone is what wakes you. See alarms on your laptop.

Sources and further reading

• Who invented the alarm clock?, History.com, and Levi Hutchins, Wikipedia
• A 2,000-year history of alarm clocks, Atlas Obscura
• US Patent 183,725, Google Patents
• Clock radios, 1959, One Tube Radio, citing Popular Science
• Wake Me Up, Series 3, Edison Research
• Sleep Cycle celebrates 10 years, Sleep Cycle
• Escalation policies, PagerDuty
• Escalating, incident.io
• Being on-call, Google, Site Reliability Engineering
• An in-situ study of mobile phone notifications, Pielot, Church and de Oliveira, MobileHCI 2014, and the 2018 follow-up
• Teens are bombarded with hundreds of notifications a day, Common Sense Media, 2023
• Mobile app push notification benchmarks for 2026, Airship
• You're distracted even when you ignore that text, APS, on Stothart, Mitchum and Yehnert, 2015
• Don't hit snooze on new research about waking up, Mass General Brigham, 2025
• Is snoozing losing?, Sundelin, Landry and Axelsson, Journal of Sleep Research, 2023
• Sleep inertia, Tassi and Muzet, Sleep Medicine Reviews, 2000
• Benefits of recruiting participants with friends, Wing and Jeffery, 1999
• Exergame partner study, Forlenza, Kerr, Irwin and Feltz
• Social facilitation: a meta-analysis of 241 studies, Bond and Titus, 1983
• stickK data on referees and stakes, HarvardX, and a 2024 study of stickK commitments
• Apple AlarmKit documentation

LFG Alarm is not affiliated with PagerDuty, incident.io, Google, Sleep Cycle, Sleep as Android, X, Twitch, YouTube, Luma, Partiful, FOMO or GMGN.