Files
Empryo/mintlify-docs/concepts/intelligence.mdx
T
PouiiroandSoulForge 350670c10b chore: governance, build hardening, mintlify sweep
- governance: CODEOWNERS, GOVERNANCE.md, PRIVACY.md, FUNDING.yml, PR template
- CONTRIBUTING.md: in-scope/out-of-scope contribution policy
- SECURITY.md: drop stale supported-versions table
- scripts/build.ts: minify + sourcemap:none + abs-path scrub + sentinel guard under NODE_ENV=production
- mintlify: rename-refactor sample, broken paths, theme list (36), casing, license name

Co-Authored-By: SoulForge <[email protected]>
2026-05-10 23:50:11 +02:00

59 lines
1.8 KiB
Plaintext

---
title: "Code intelligence"
description: "LSP, AST, and fallbacks — the agent sees your code like an IDE."
icon: "brain"
---
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
| Operation | Examples |
|-----------|----------|
| **Go to definition** | "where is `parseConfig` defined?" |
| **Find references** | "who calls `parseConfig`?" |
| **Rename** | "rename `useChat` to `useConversation` everywhere" |
| **Type info** | "what's the return type of `fetchUser`?" |
| **Diagnostics** | "any errors in this file?" |
| **Call hierarchy** | "what does `buildTools` call?" |
All of these come through the `navigate` and `analyze` tools.
## How it picks a backend
```
LSP → ts-morph (TS/JS) → tree-sitter (33+ langs) → regex
```
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:
```
/lsp status
```
Install more servers through the Mason registry:
```
/lsp install
```
## 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.