Skip to main content
SoulForge embeds a real Neovim instance — your config, your plugins, your LSP servers. The AI agent can read, edit, navigate, and inspect code through the same editor you use.

​
Overview

The editor panel runs alongside the chat. Toggle it with Ctrl+E or /editor. The agent accesses it through the editor tool with 18 actions covering reading, editing, navigation, LSP operations, and terminal output.

​
Key shortcuts

​
Neovim configuration

SoulForge supports three Neovim config modes, selectable via /nvim-config:
On first launch with default mode, SoulForge bootstraps LazyVim plugins and installs LSP servers via Mason for all detected project languages. This is a one-time setup.

​
Editor tool actions

The editor tool provides 18 actions for the AI agent. These require the editor panel to be open (Ctrl+E).

​
Reading & inspection

​
Editing

​
LSP operations

​
Editor integrations

Configure which LSP features the agent can access via /editor settings:

​
Agent access modes

Control when the agent can use the editor tool:

​
Dual LSP backend

The agent always has LSP access regardless of editor state:
  • Neovim bridge — When the editor is open, LSP requests route through Neovim’s running servers via Lua RPC. Zero startup cost since servers are already warm.
  • Standalone client — When the editor is closed, SoulForge spawns LSP servers directly as child processes. Full protocol support.
Both backends support: definitions, references, hover, diagnostics, rename, code actions, call/type hierarchy, and formatting.

​
Mason auto-install

On first editor launch, SoulForge detects project languages and installs appropriate LSP servers via Mason. Servers are stored in ~/.soulforge/lsp-servers/ and discovered automatically.

​
Vim hints

Toggle Neovim keybinding hints in the UI with /vim-hints. When enabled, common Vim keybindings are shown in the editor footer.

​
Split ratios

Cycle the editor/chat split with /editor split: