English | 日本語

KeyProbe

Test every key on your keyboard from Raycast.
A native, translucent panel that highlights each key as you press it — confirm a custom keyboard actually works at the OS level.

Features

• Highlights a key while held, then marks it "tested" once released, so you can see at a glance which keys you haven't tried yet
• Built-in ANSI / JIS / ISO layouts, auto-detected from your attached keyboard's hardware type
• Currently 50+ bundled custom keyboard layouts (Corne, Lily58, Planck, HHKB, Keychron Q11, moNa2, Kinesis Advantage 360, and more), searchable via Select Keyboard Layout
• Keys with no fixed OS keycode (layer keys, media keys) are drawn as non-testable — after switching layers, press the key and confirm it actually types what you expect
• Reset button clears all state without closing the panel

Setup

1. Run Open KeyProbe from Raycast
2. If macOS asks, grant Input Monitoring to Raycast, then run the command again

[!IMPORTANT] KeyProbe's helper runs as part of Raycast, so macOS checks Raycast's permissions when it reads keystrokes. If Raycast already has Accessibility permission (it usually asks for this during setup), nothing else is needed. Otherwise, enable Raycast in System Settings → Privacy & Security → Input Monitoring, then run Open KeyProbe again. Until it's granted, the panel doesn't open — Raycast opens the Input Monitoring settings for you instead.

Choosing a layout

• The Keyboard Layout preference sets the default: Auto-Detect, ANSI, JIS, or ISO
• Select Keyboard Layout searches all bundled layouts — including the custom keyboards — and switches live, even while the panel is open

[!NOTE] Auto-Detect reads the physically attached keyboard's hardware type, not your macOS input source language. An ANSI-shaped board stays "ANSI" even if its firmware sends JIS key combos; pick JIS explicitly to test those.

Known limitations

[!WARNING] Hardware media/volume/brightness keys arrive as a different event type this tool doesn't capture, so they won't register at all — not even as an unmapped key.

• Small ZMK-firmware layouts like cornix couldn't have their default keymap auto-parsed (heavy macro use), so their layout was built from a reference image of the actual default keymap instead. To test a key that isn't shown on the board, check the unmapped-key readout at the top of the panel, or switch to another Keyboard Layout such as the 100% (ANSI) full-size board