Use the Hotkey Manager Outside React Components

This is an advanced guide. When you use TanStack Hotkeys with React, you usually never need to use the hotkey manager yourself. useHotkey and useHotkeys register hotkeys with it, unregister them when the component unmounts, apply provider defaults and scopes, and keep callbacks current. Use the manager directly only for code that runs outside components, and in tests.

Every hotkey goes to one HotkeyManager, shared by the whole page. The manager attaches the keyboard listeners, matches key presses to hotkeys, tracks sequence progress, and decides which scopes are active. Get it with getHotkeyManager():

import { getHotkeyManager } from '@tanstack/react-hotkeys'

const manager = getHotkeyManager()

Register a hotkey

manager.register takes the same hotkeys and options as useHotkey, and returns a handle:

const handle = manager.register('Mod+K', () => openCommandPalette())

handle.setOptions({ enabled: false }) // Merges new options into the registration
handle.callback = () => openSearch() // Replaces the callback
handle.unregister() // Removes the hotkey

A hotkey registered with the manager differs from one registered with a hook:

It stays registered until you call unregister().
Provider defaults and scopes don't apply. It uses the built-in defaults and belongs to the 'global' scope, unless you pass scope.
Its target must be an element, document, or window, not a ref.
During server rendering, register returns a handle that does nothing.

For example, code that sets up a chart library outside React can register the chart's hotkeys and return a function that removes them:

import { getHotkeyManager } from '@tanstack/react-hotkeys'

export function attachChartHotkeys(chart: Chart, element: HTMLElement) {
  const manager = getHotkeyManager()
  const handles = [
    manager.register('I', () => chart.zoomIn(), { target: element }),
    manager.register('O', () => chart.zoomOut(), { target: element }),
  ]

  return () => handles.forEach((handle) => handle.unregister())
}

Read registrations

In a component, read registrations with useHotkeyRegistrations. See List the hotkeys on screen.

Outside components, ask the manager:

manager.getRegistrationCount() // How many hotkeys are registered
manager.isRegistered('Mod+S') // Whether any registration matches
manager.isRegistered('Escape', panelElement) // Whether one matches on that target

isRegistered compares hotkeys the way duplicate detection does, so Meta+S matches a Mod+S registration on macOS.

manager.registrations is a TanStack Store that holds every registration in a Map, keyed by id. Subscribe to it to run code when registrations change:

const subscription = manager.registrations.subscribe((registrations) => {
  console.log(`${registrations.size} hotkeys registered`)
})

subscription.unsubscribe()

The store also updates each time a hotkey fires and each time a sequence advances, so keep subscribers fast. Registrations in the store include their callbacks. To get the view that useHotkeyRegistrations returns, without the callback, pass a registration to toHotkeyRegistrationView.

Activate a scope

In components, create scopes with HotkeysProvider. See HotkeysProvider and Scopes. For UI that React doesn't render, such as a dialog from another library, activate the scope on the manager, and pass scope to the hotkeys that belong to it:

const releaseScope = manager.activateScope('image-viewer', { exclusive: true })
const close = manager.register('Escape', () => viewer.close(), {
  scope: 'image-viewer',
})

// When the viewer closes
close.unregister()
releaseScope()

activateScope returns a function that releases the scope. A scope stays active until every activation of it is released. activateScope takes two options:

exclusive suspends every other scope, including 'global', while this scope is active. Pass { allow: ['global'] } to keep the listed scopes working.
parent names the scope this one is nested in, so this scope takes precedence over it. The default is 'global'.

Read scope state

manager.isScopeActive(scope) returns whether hotkeys in a scope can fire. useHotkeyRegistrations re-renders when scopes change, so a list filtered with isScopeActive stays current.

manager.scopes is a store with these fields:

active lists the activated scopes, lowest precedence first. 'global' is always active, so it isn't listed.
exclusive is the exclusive scope that owns the keyboard, or null.
allowed lists the active scopes that the exclusive scope allows.
suspended lists the active scopes that can't fire because another scope is exclusive. It can include 'global'.

To read it in a component, subscribe with React's useSyncExternalStore:

tsx

import { useSyncExternalStore } from 'react'
import { getHotkeyManager } from '@tanstack/react-hotkeys'

const manager = getHotkeyManager()

function subscribe(onChange: () => void) {
  const subscription = manager.scopes.subscribe(onChange)
  return () => subscription.unsubscribe()
}

function getScopes() {
  return manager.scopes.state
}

function KeyboardOwner() {
  const scopes = useSyncExternalStore(subscribe, getScopes, getScopes)

  return scopes.exclusive ? <p>Shortcuts belong to {scopes.exclusive}</p> : null
}

The devtools show the same scope state without any code.

Reset sequence progress

manager.resetSequenceProgress() clears the steps the user has pressed in every sequence. Call it when an action in your app should cancel a sequence the user has started.

Match a sequence on your own

createSequenceMatcher matches one sequence against keyboard events you pass it, without registering anything with the manager. Use it in a keyboard listener you already own:

import { createSequenceMatcher } from '@tanstack/react-hotkeys'

const matcher = createSequenceMatcher(['G', 'G'], { timeout: 1000 })

document.addEventListener('keydown', (event) => {
  if (matcher.match(event)) scrollToTop()
})

The matcher tracks its own progress. getProgress() returns the number of steps matched so far, and reset() starts over. It doesn't skip text fields, prevent the browser's action, or check scopes, so handle those in your listener if you need them.

Reset the manager in tests

The manager lasts as long as the page, so a test environment keeps it between tests. Components that unmount unregister their hotkeys, but hotkeys registered with manager.register and scopes activated with activateScope stay. Reset the manager after each test:

tsx

import { afterEach, expect, it, vi } from 'vitest'
import { render } from '@testing-library/react'
import { HotkeyManager, useHotkey } from '@tanstack/react-hotkeys'

afterEach(() => {
  HotkeyManager.resetInstance()
})

it('saves with Mod+S', () => {
  const save = vi.fn()

  function Editor() {
    useHotkey('Mod+S', save, { platform: 'mac' })
    return null
  }

  render(<Editor />)
  document.dispatchEvent(
    new KeyboardEvent('keydown', { key: 's', metaKey: true, bubbles: true }),
  )

  expect(save).toHaveBeenCalledOnce()
})

resetInstance removes every listener and registration, and the next getHotkeyManager() call creates a new manager. Held keys have their own tracker, so reset it with KeyStateTracker.resetInstance() in tests that read held keys.

platform: 'mac' makes Mod mean Command, so the test passes on every operating system. To set it for every hotkey in a test, pass it in HotkeysProvider default options: defaultOptions={{ hotkey: { platform: 'mac' } }}.

The HotkeyManager reference lists every method.