Use case or problem
While Obsidian already provides built-in Vim key bindings, many users—especially those in the modern terminal ecosystem—have migrated to Helix. Helix offers a modal editing experience with a selection-first movement model (select -> action) and built-in visual hints that many find more intuitive and ergonomic than Vim’s command-first model.
Currently, using Helix-style navigation in Obsidian requires third-party plugins, which can lead to inconsistencies during editor core updates and missing integration with Obsidian’s native UI elements (such as mode indicators in the status bar).
Proposed solution
Integrate native Helix key bindings support into Obsidian core as a first-class modal editing option alongside Vim.
- Native Helix keymap support: Add a toggle in settings to enable Helix modal editing natively.
- Status Bar Mode Indicator (for both Vim and Helix): Introduce an official option to display the active modal mode (e.g.,
NORMAL,INSERT,SELECT) directly in the status bar. This would provide immediate visual feedback for both Vim and Helix users without relying on third-party CSS snippets or extra community plugins.
Native integration ensures low latency, long-term stability, and seamless compatibility across all core editing features and platforms.
Current workaround (optional)
Users currently rely on the community plugin Helix Keymap, which itself leverages the CodeMirror Helix Extension.
While this plugin demonstrates that Helix-style keybindings are fully feasible and highly requested, community plugins can lag behind major CodeMirror or Obsidian updates. Having this natively maintained alongside Vim bindings would guarantee stability and offer a smoother out-of-the-box experience for modal editing enthusiasts.