Skip to main content
SoulForge gives the agent the same code intelligence your IDE has: go-to-definition, references, rename, diagnostics, type info. It tries LSP first, falls back to AST tools, then tree-sitter, then regex. This replaces grep-and-read. The agent navigates the code graph by symbol, not by pattern matching across files. Cheaper, faster, correct. You don’t configure this. It picks the best available backend for every operation.

​
What it can do

All of these come through the navigate and analyze tools.

​
How it picks a backend

If LSP isn’t attached for your language, the agent still works — the lower tiers cover most queries.

​
LSP always-on

The agent has LSP access even when the editor panel is closed. When you open Neovim (Ctrl+E), requests route through your LSP servers there. When it’s closed, SoulForge spawns standalone servers. Check what’s attached:
Install more servers through the Mason registry:

​
After every edit

SoulForge snapshots diagnostics before the edit, compares after, and tells the agent:
  • New errors it just introduced
  • Errors it just fixed
  • Errors in other files caused by the edit
The agent sees this instantly — no need to run a full typecheck.