Run on OS login
An installed app can start when the person logs in to their computer.
In one line
Can start an installed app when you sign in, only if you choose
An installed app can start when the person logs in to their computer.
Set by the person, not the site, via about://apps, or by IT policy. No site can enable it silently.
What it can and can't do
What the user does: You turn on Start app when you sign in, or your IT team sets it
It can
- Start the app when you sign in once you turn it on
- Start through an IT policy on managed computers
- Stay off until you or IT turn it on
It cannot
- Turn itself on without you
- Start for a site that is not installed
- Work in Safari, Firefox or on phones
- Be turned on from the page, since the person sets it
How it differs between platforms: Chrome and Edge on computers only, and still in testing. Not on phones, Safari or Firefox.
Browser support
| Browser | Status | First version | Note |
|---|---|---|---|
| Chrome | Behind a flag | 91 | user setting |
| Edge | Behind a flag | 91 | user setting |
| Firefox | Not supported | Not available | None |
| Safari | Not supported | Not available | None |
| Safari on iPhone | Not supported | Not available | None |
| Chrome on Android | Not supported | Not available | None |
| Samsung Internet | Not supported | Not available | None |
How a site asks for it
| API | No web API; WebAppSettings policy run_on_os_login: blocked, run_windowed, allowed |
| How access is granted | settings |
| What the user sees | User toggles Start app when you sign in |
| Needs a secure context (HTTPS) | Yes |
| Needs a user gesture | No |
| How long it lasts | Per origin |
| How to take it back | Site settings |
| Inside an iframe | Same as top level; cross-origin iframes need a permissions policy where listed |
Typical flow
- Call the API
- Browser applies its access rules
- Page receives the result
Data you get
What comes back: An installed app can start when the person logs in to their computer.
Shape: object
How often: on demand
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
run_on_os_login | enum | None | blocked, run_windowed, allowed | enterprise policy |
Technical limits
- A manifest member was only proposed
- Never silent
The story
What it is
An installed web app can start by itself when you sign in to your computer.
For you
You may see a prompt or a setting asking if the app should start when you log in. If you say yes, it opens right away each morning. You can turn it off in app settings.
For makers
Makers want chat, music and work apps to be running and ready for alerts. It raises daily use. It uses memory and startup time, so a person must opt in.
Where you see it
| Type | Example | Apps |
|---|---|---|
| messaging | A chat web app starts at login so you do not miss messages. | Slack |
| music | A web music player opens at login and resumes your playlist. | None named |
| enterprise | A company dashboard app starts when staff sign in. | None named |
| productivity | A web task app opens at login to show today's list. | Todoist |
| games | A web game launcher starts at login to check for updates and friend invites. | None named |
| video | A web meeting app starts at login to be ready for calls. | Microsoft Teams |
| health | A web health monitor app starts at login to track your day. | None named |
Risks
- Slows startup
- Runs when not wanted
What the platform says
- Google Chrome: Run on OS login. Lets installed web apps launch when you sign in, so chat or music apps are ready from the start.
Good uses and abuse
Legitimate uses
- Chat apps
Known abuse
- None
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 1 of 5 | How revealing the data is |
| Utility | 2 of 5 | How useful it is to honest apps |
| Friction | 3 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2021-05, Chrome 91: Run on login on Windows, Linux, macOS
Sources
How well checked: Based on official documentation.