--no-first-run
What does --no-first-run do?
Skip First Run tasks as well as not showing additional dialogs, prompts or bubbles. Suppressing dialogs, prompts, and bubbles is important as this switch is used by automation (including performance benchmarks) where it's important only a browser window is shown. This may not actually be the first run or the What's New page. Its effect can be partially ignored by adding kForceFirstRun (for FRE), kForceWhatsNew (for What's New) and/or kIgnoreNoFirstRunForSearchEngineChoiceScreen (for the DSE choice screen). This does not drop the First Run sentinel and thus doesn't prevent first run from occurring the next time chrome is launched without this flag. It also does not update the last What's New milestone, so does not prevent What's New from occurring the next time chrome is launched without this flag.
Usage
CLILaunch Chrome with --no-first-run using CLI
chrome --no-first-runPuppeteerLaunch Chrome with --no-first-run using Puppeteer
const browser = await puppeteer.launch({
args: ['--no-first-run']
});PlaywrightLaunch Chrome with --no-first-run using Playwright
const browser = await chromium.launch({
args: ['--no-first-run']
});SeleniumLaunch Chrome with --no-first-run using Selenium
from selenium import webdriver
options = webdriver.ChromeOptions()
options.add_argument('--no-first-run')
driver = webdriver.Chrome(options=options)