1.63.0 (2026-11-15)
This release adds vim mode, which reads the text on screen so you can move over it and edit it with vim's keys in any app, with no accessibility tree. Hint labels can alternate hands, neru describe tells scripts and agents what the installed build supports, and a round of Linux fixes covers Wayland, KDE, GNOME, niri and X11.
Migration Guide
Note
Held-key glides feel different. With held_repeat on, a glide now eases up to speed over about 120 ms and bends on turns instead of cornering. A move_mouse_relative binding with both --dx and --dy set glides at its own angle and step length, so --dx 10 --dy 5 moves at about 27 degrees instead of 45. The default arrow and hjkl bindings only get the ease-in. Releasing still stops the cursor dead.
Note
Linux: on Wayland without the keyboard proxy, neru action feed now refuses a key while a mode is open, instead of the key coming straight back into the mode.
Vim mode
neru vimputs a cursor on the text of the focused window, or the whole screen. Motions, counts, text objects, search, registers, macros and.work as in vim- Edits happen in the app. Vim mode clicks the caret into place, selects, types, then reads the screen again. A put types the register's text, so the clipboard is left alone. A yank copies the text as read
Return,gc,grandgmclick at the cursor, and a count makes a double or triple click.sjumps to any text by label, and icon-only buttons are reachable as□- Columns, sidebars, cards and inputs are containers you can move between
- The
:line takes:s/old/new/with live highlights,:q,:leftclick,:rightclickand:middleclickwith an optional count,:leftdownand:leftupto drag, and:movemouse(alsogh) - Scroll keys scroll the app with the overlay up, and vim reads again once the page settles
[vim.keymaps.normal]and[vim.keymaps.visual]remap keys in vim notation, asnnoremapdoes.[vim.hotkeys]runs Neru actions ahead of vim. Both ship empty- An edit containing a character no key types, such as a letter outside ASCII, is refused with the reason in the status bar
- macOS: reads every script it knows. The first session after an install or macOS update spends about 50 seconds preparing text recognition, then a window reads in about 0.4 s
- Linux: reads with tesseract, Latin plus any other-script language the locale names whose data is installed. On Wayland without the keyboard proxy, edits are refused
- Windows: reads the first language in the account's list that has an OCR pack
[hotkeys]
"Primary+Shift+V" = "vim"
[vim]
capture_scope = "window" # or "screen"
[vim.keymaps.normal]
"<Space>j" = "<Plug>(jump)"
"H" = "^"Alternating-hand hint labels
hints.label_alternation = "halves"takes each key of a multi-key label from the opposite hand to the key before it, so labels likejkorklbecomeahorls- The hands come from
hint_characters. The first half is one hand and the second half the other, so the defaultasdfghjklsplits intoasdfgandhjkl - With the default characters it applies up to 180 hints. Past that, labels are the usual ones, so nothing goes unlabeled
- Needs at least four hint characters. The default stays
"none"
[hints]
label_alternation = "halves"Ask the build what it supports
neru describelists every mode, flag, action, config option, event and hook variable this build reads, with the platforms each works on and whether it works here.--jsonprints the whole objectneru schema ipcandneru schema configprint the JSON Schemas this build speaksneru agent-guideprints a short guide for AI agents, written for this build- None of them needs a running daemon or a config. The daemon also answers
describeover IPC, even while stopped
neru describe --json | jq -r '.actions[] | select(.here) | .name'Fixes
- Linux: Wayland overlays no longer stop taking keys mid-session, which sent grid labels and Escape to the app underneath. This hit setups where Neru reads keys through the overlay
- Linux: on Wayland with smooth scroll off, the first scroll after launch arrives, and scrolls go the way they are sent under natural scrolling
- Linux: a Wayland seat with no keyboard, such as headless sway, no longer kills the overlay, and Neru picks up the keyboard layout once a keyboard appears
- Linux: KDE Plasma no longer drops clicks made at the cursor, about six in ten before
- Linux:
--modifierclicks and scrolls keep their modifier on GNOME, so ctrl-click and ctrl-scroll work - Linux: on niri, hints, grids and vim line up with windows that have a border
- Linux: on X11, hints and grids cover the whole desktop after a monitor is added or the layout grows, without a restart
- Nix: the x86_64 Linux package installs again on current nixpkgs
- The tray icon no longer shows a "Running" or "Paused" tooltip
Features
- cli: add describe, schema and agent-guide (#1983) (8113987)
- hints: alternate hands in multi-key hint labels (#1944) (e108948)
- vim: add vim mode (#1921) (0870c99)
Bug Fixes
- glide held
move_mouse_relativekeys at the angle of their step (#1948) (782797c) - linux: draw hints and grids across the whole X11 desktop after it grows (#1966) (4cb4ac6)
- linux: keep modifiers on clicks and scrolls on GNOME (#1965) (59c1029)
- linux: keep the first scroll after launch on Wayland (#1956) (dd9ac4e)
- linux: keep the overlay alive on a Wayland seat with no keyboard (#1959) (09b7609)
- linux: keep Wayland scrolls going the way they are sent under natural scrolling (#1957) (0e4bddd)
- linux: place niri window origins inside the tile border (#1951) (d50d679)
- linux: read the keyboard layout on a Wayland seat that starts with no keyboard (#1960) (5fd1c58)
- linux: stop KDE dropping clicks made at the cursor (#1963) (19d3cf1)
- linux: stop Wayland overlays from losing keyboard input (#1940) (c9a5e85)
- nix: stop the x86_64 Linux package segfaulting on current nixpkgs (#1935) (86a0ddc)
- systray: remove tooltip from the tray icon (#1937) (078eb54)