1. Install
Install from the extension store for your browser:
Optimised for Chromium-based browsers (Chrome / Edge). See Browser Support for details.
2. Configure the shortcuts
After installing, the browser may not honour the recommended defaults, in that case you can set them up manually:
| Shortcut | Palette | What you search |
|---|---|---|
| Cmd+P Ctrl+P | Bookmarks | Everything in your bookmarks |
| Cmd+Shift+P Ctrl+Shift+P | Commands | Built-ins, scripts, bookmarklets |
These may conflict with native browser shortcuts like the one for the print dialog or open private window (Firefox). You can rebind them:
- Chrome / Edge — open
chrome://extensions/shortcuts, find Hacklets, and click the pencil icon next to a shortcut. Extension shortcuts take precedence over browser-native ones. - Firefox — open
about:addons, select Hacklets, and edit shortcuts via the gear menu. Native shortcuts win here, so if a shortcut is not working pick a different combination or disable the native one inabout:keyboard.
See Shortcuts for more information and troubleshooting conflicts.
3. Allow user scripts permission
Hacklets can run your own JavaScript through the browser’s user scripts API, which is off by default. Until it is enabled, bookmarklets and user scripts won’t run.
- Open the settings page (right-click the extension icon → Options).
- If a banner reads “User Scripts Permission is Disabled”, click Grant
Permission or Open Extension Settings:
- On Chrome, this opens the extension page — toggle the User scripts permission on, then return to the settings page.
- On Firefox, the browser shows a permission prompt — accept it.
- The banner disappears once the permission is active.
4. Pick a user scripts folder (optional)
Hacklets turns any local folder of .js files into palette commands.
- Open the settings page (right-click the extension icon → Options).
- Click Choose Folder and select the folder containing your scripts.
- Open the commands palette — your scripts appear alongside the built-in commands.
The folder is remembered locally in your browser. Scripts are read from disk only when a command runs. See Scripts for details.
5. Start creating your own scripts (optional)
Create .js files in your folder, each with a UserScript metadata header:
// ==UserScript==
// @name Greet the page
// @emoji 👋
// @match *://*/*
// ==/UserScript==
const name = prompt('What should I call you?')
alert(`Hello, ${name}!`)
The header’s @name becomes the command title, @emoji the icon, and @match
the pages the script appears on.
Use the built-in script editor to create and edit scripts.
What’s next
- Making the Most of Search — learn how the search works to streamline your workflow.
- User Scripts — run JavaScript from a local folder.
- Bookmarklets — run JavaScript from your saved bookmarklets.
- Keyboard Shortcuts — customize every shortcut.
- Command Reference — every built-in command.