Roadmap

What Neru intends to work on next, and in what order. What works today is in the Capability Matrix, and what is missing under Known Gaps.

Where things stand

Each platform’s label is in Platform status. Linux and Windows have nothing left to build for theirs. A platform reaches Stable through use, not features, per What the labels mean, so the roadmap has no platform feature list.

Near term

1. Prove Linux and Windows in use. A bug filed against either platform outranks any new capability. Windows has had little real-world use, so expect bugs and report them, such as #1483: an injected scroll on Windows carries modifiers the user is physically holding.
2. Reliability over features. Startup, config reload and mode transitions fail loudly and recover cleanly. Regressions here are fixed before anything else ships.
3. More automated checks. Anything that could break without an error gets a test. Config reload and the platform contracts have the fewest so far.

Open direction

Ideas with maintainer interest and no schedule. Each is an issue rather than a promise, and a Discussion is where a new one starts (Contributing).

• React to a real mouse click inside a mode (#1417).
• Subgrid preview in recursive grid, the boundary counterpart of sub_key_preview (#1116).
• Auto-refresh hints when the accessibility tree changes (#1002).

Helping out

Where contributions help most is in CONTRIBUTING.md.