Keys in Neovim

The plugin keeps no list of keys of its own. When the server starts, it announces its commands with their default keys (org-lsp manifest prints them), and the plugin binds the keys of the vim preset, which are nvim-orgmode's defaults. Keys for Org files, the agenda, the date prompt and capture buffers are local to those buffers; the keys listed under Anywhere are global.

g? shows the keys of the buffer at hand, and :nmap <buffer> in an Org buffer lists what is bound there, each key described by the title of its command. neovim.org says how to install and set up the plugin.

The keys#

Anywhere#

In Org files#

In a capture buffer#

In the agenda#

¦ stands for |, which an Org table cannot hold.

In the date prompt#

In column view#

Without a default key#

¹ Where the command does not apply, the key does what it does in any buffer: <C-a> off a timestamp still increments the number under the cursor, <S-Right> off a timestamp goes a word right (and on a headline or an item too, as org_support_shift_select says), and <CR> in a source block's code is Vim's own.

The plugin's own keys#

The plugin adds keys of its own, which only an editor can carry out:

In the agenda, Neovim's own K (vim.lsp.buf.hover()) shows the entry of the line, highlighted as Org files are: the plugin makes the hover's float an Org buffer of the server's. Emacs's K (org.agenda.habits) has no key there; hover maps the plugin's own float to another key.

A capture buffer is an Org file, so it has the keys of Org files as well as its own; there <Leader>or refiles the captured entry rather than the subtree at the cursor.

How they behave#

• Counts work as in Vim: 3<C-a> adds three to the part of the timestamp under the cursor, 2<S-Right> moves an agenda entry two days.
• Repeat: every key in Org files changes the text, and . repeats the last of them, with a new count if you type one (., 3.). A command that asks for something asks again.
• In Visual mode the keys of the commands Org gives a region work on the selection, as Emacs's on its active region: >> and << demote and promote the headlines selected (or indent and outdent the items), <Leader>o* and <Leader>o- turn the lines into headings and items, <C-Space> toggles the checkboxes, <Leader>oi<Bar> makes a table of them, <Leader>oib and <Leader>oiD wrap them in a block or a drawer; <Leader>or refiles the subtrees selected, <Leader>ols stores a link that searches for the text selected and <Leader>oli makes it the description of a link.
• Keys with a meaning of their own (marked ¹) give it back where the command does not apply, so <C-a>, <C-x>, <S-Up> and <S-Down> still work on ordinary numbers and lines.
• RET and a completion menu: while one is open (Vim's, nvim-cmp's or blink.cmp's), <CR> is the menu's; <S-CR> closes it and runs its command.
• <S-CR> is RET that continues lists: on the line of a list item's bullet it makes the next item, numbered and with a checkbox as M-RET makes it, and elsewhere it is Org's RET. <CR> does that too with return_uses_meta_return.
• <Leader><CR> and its neighbours put the new heading, item or table row below the cursor's line, wherever on it the cursor is: never above it, and nothing is split. Typing goes on in insert mode.
• K in the agenda shows the line's entry in a float at the cursor: its headline and its text, each drawer folded to its first line, highlighted as Org files are. A second K goes into the float, q there closes it, and moving the cursor closes it too.
• cid leaves the cursor where it was in the timestamp it changes, and a date asked for in the calendar goes back to the window it was asked from.
• Questions are asked in the editor's own way:
  • a date (<Leader>ois, J in the agenda) opens Emacs's calendar, with the keys under In the date prompt; i there asks for the date as text with vim.ui.input, read as Org reads it (fri 10:00, +2d, 2/15); t there picks a time: a Time: line shows it, h and l choose the hour or the minutes, k and j move it up or down (the minutes by org_time_stamp_rounding_minutes), and t again goes back to the days, keeping the time;
  • one key (a TODO keyword with a key, as TODO(t), a capture template, or a view in the agenda menu) is read as soon as it is typed, with the choices listed in a window at the bottom; <Esc> gives up;
  • a choice from a list (refile targets) goes through vim.ui.select, so a picker plugin that replaces it is used;
  • text (a capture prompt) goes through vim.ui.input;
  • a state note (a keyword with @, as WAIT(w@)) is written in a note buffer that opens like a capture buffer, as Emacs's *Org Note*: <C-c> stores it, <Leader>ok changes the state without it.
• Messages: what Emacs says when a command is done (Priority of current item set to B, Scheduled to <2026-05-22 Fri>) goes through vim.notify, and so do commands' errors (No timestamp at the cursor).
• Capture buffers open in insert mode, where the template's %? was.

Changing them#

Keys are set with mappings, in setup() or in vim.g.org_lsp before the plugin loads. It has one table per scope: global, org, agenda, calendar, capture and columns. In a scope, a command (the second column above, or one of the plugin's own names) maps to:

• a key, which takes the place of the command's default keys;
• a list of keys, to have more than one;
• false, to leave the command without a key.

Commands that are not listed keep their default keys.

require('org-lsp').setup({
  mappings = {
    -- Org's own key for the agenda, and a key for the TODO list.
    global = { ['org.agenda.dispatch'] = '<Leader>a', ['org.agenda.todos'] = '<Leader>oT' },
    org = {
      ['org.todo'] = { 'cit', '<Leader>ot' },   -- two keys
      ['org.todo.next'] = '<C-n>',              -- a command without a default key
      ['org.todo.previous'] = false,            -- no key
      ['org.shift.right'] = '<S-Right>',        -- Org's S-<right>: date or TODO state
      ['org.shift.left'] = '<S-Left>',
      global_cycle = '<Leader><Tab>',           -- the plugin's own command
    },
    agenda = { ['org.agenda.goto.date'] = 'gd', quit = { 'q', '<Esc>' } },
  },
})

To set no keys in one scope, give false for the scope; the plugin's own keys in it go too. To set no keys at all, give false for mappings:

vim.g.org_lsp = { mappings = { org = false } }   -- nothing in Org files
vim.g.org_lsp = { mappings = false }             -- nothing anywhere

Calling setup() again changes the keys of buffers opened after it, and the global ones at once.

Your own keys#

Any command can be run from a key of your own with require('org-lsp').run, which tells the server where the cursor is:

vim.api.nvim_create_autocmd('FileType', {
  pattern = 'org',
  callback = function(args)
    vim.keymap.set('n', '<M-Right>', function()
      require('org-lsp').run('org.shift.right', { count = vim.v.count })
    end, { buffer = args.buf, desc = 'Org: date later or next TODO state' })
  end,
})

Keys set this way are not repeated by .; keys set through mappings are. run also takes the plugin's own names (cycle, global_cycle, quit, hover).

From the command line#

:Org runs a command by its name without the org. prefix, with completion: :Org todo.next, :Org agenda.todos. Words separated by spaces are joined with dots, so :Org agenda todos works as well, and a group on its own runs its dispatcher: :Org agenda.

The editing commands are also code actions, so vim.lsp.buf.code_action() (gra) lists those that apply at the cursor.