Skip to main content
Celerity is a Chrome extension that overrides the new tab page. You can install it in seconds from the Chrome Web Store, or load it directly from the source folder if you prefer to inspect or modify the code before running it. Both paths end in the same place: every new tab you open launches Celerity.

​
Requirements

  • Google Chrome (any recent stable release). Celerity uses Manifest V3 and standard Chrome extension APIs — no additional software required.

​
Installation

The Chrome Web Store path handles everything automatically: Chrome downloads, verifies, and activates the extension for you.
1

Open the Celerity listing

Navigate to the Celerity page on the Chrome Web Store.
2

Click 'Add to Chrome'

Click the Add to Chrome button on the listing page. A confirmation dialog lists the permissions the extension requests.
3

Confirm the installation

Click Add extension in the dialog. Chrome downloads and activates Celerity immediately.
4

Open a new tab

Press Ctrl + T (or ⌘ T on macOS). Celerity now appears instead of the default new tab page.

​
After installation

Once Celerity is active, every new tab you open displays the command launcher grid. No configuration is required to start using it — the 12 built-in shortcuts are ready immediately.

​
First-visit guidance

The first time you open a new tab after installation, the compass (help) icon in the top-right corner pulses with a border animation. Click it to read a quick overview of the commands and keyboard shortcuts. Once you close the help panel, the gear (settings) icon pulses in turn, inviting you to explore shortcut management.
Celerity requests only the storage permission, which it uses to save your shortcuts and theme preference to your browser’s local storage. The activeTab permission is listed as optional and is never requested during normal use.

​
Permissions reference

The extension overrides the new tab page via Chrome’s chrome_url_overrides.newtab mechanism, loading index.html in place of the default page. No remote code is executed; all scripts are bundled locally and governed by a strict Content Security Policy.