Feature request: Neovim IDE context provider for existing Codex CLI sessions

What variant of Codex are you using?

CLI

What feature would you like to see?

Support Neovim as an IDE context provider for /ide, so Codex can include open buffers, current file, selection/range, cwd, and diagnostics similarly to the VS Code-compatible extension.

Current behavior

/ide exists in the CLI, but official IDE context integration appears limited to VS Code-compatible editors and JetBrains.

Why this matters

Many terminal-first users run Neovim and Codex CLI side by side in terminal splits, tmux, or Ghostty panes. Today they must manually mention files or paste selected code, which loses active selection, open-buffer, cwd, and diagnostics context.

This request is not primarily about launching Codex inside Neovim. Community plugins can already open Codex in a Neovim terminal. The missing piece is a supported way for an existing Codex CLI session to receive IDE/editor context from Neovim, similar to /ide with supported IDE integrations.

Possible implementation

Expose or document a stable editor-context protocol that Neovim plugins can implement, or support a first-party/community Neovim provider that can attach to an existing Codex CLI session via /ide or app-server.

Additional information

Related but not duplicates:

• #24514: /ide cannot enable IDE context from a VS Code terminal
• #3302: community codex.nvim plugin that opens Codex inside Neovim
• #21666: Codex TUI behavior inside Neovim terminal

My use case is separate from #3302: I want to keep Codex CLI running in a separate terminal pane and send Neovim context to that existing session.