Docs

Command palette

One prompt for navigation, queries, scripts and toggles, with a listener the platform cannot swallow.

Opening it

Alt+Shift+P, on any ServiceNow page.

That shortcut is declared as a browser command rather than a page listener, which matters in three cases a page listener loses: ServiceNow stops plenty of keys itself, a tab that is still loading has no listener to press yet, and only declared commands show up in chrome://extensions/shortcuts where people go to rebind things.

The palette's own in-page listener sits in the capture phase for the same reason: it sees the keystroke before the platform's handlers do.

Three shortcuts, not as many as fit

Chrome allows four suggested keys per extension, and every suggestion collides with something else you have installed. Three earn the slot:

Alt+Shift rather than Ctrl and a digit: Ctrl+1 through Ctrl+8 switch browser tabs, Chrome never hands those to an extension, and a shortcut that silently never fires is worse than no shortcut.

A browser shortcut runs the palette command of the same name, so the two can never drift.

A few commands

tt          toggle the dark theme
tn          toggle technical field names
sysid       copy the current record's sys_id
xml         open the record's XML
versions    list the versions of this record
bg          run a background script
me          who am I on this instance

Type a table name to open its list, or a partial module name to jump to it. The navigator menu is resolved from the platform's own API, so what you can reach in the palette is what you can reach in the application navigator.

Running a background script

bg takes a script and runs it through the platform's own background-script path, which means it needs the same admin that path always needed. The palette does not escalate anything; it removes the detour.

Output comes back into the panel instead of a streaming page that leaves the record you were looking at.