How it works

Documentation Index

Fetch the complete documentation index at: https://soulforge.proxysoul.com/llms.txt

Use this file to discover all available pages before exploring further.

SoulForge is three things talking to each other:

1. A live code graph — every file, symbol, and import, ranked by importance. Updated as you work.
2. An agent loop — reads, edits, tests, commits. Can dispatch parallel sub-agents.
3. Your Neovim — embedded. The agent edits through the same editor you use.

​

The agents

Configure which model each one uses in the task router.

​

What the agents share

When Forge dispatches multiple sub-agents in parallel, they coordinate through the AgentBus:

• File cache — first reader caches; others reuse.
• Tool cache — read-only tool results shared across agents and dispatches.
• Edit lock — concurrent writes to the same file are serialized.
• Findings — one agent’s discovery reaches the others at their next step.

Result: N agents don’t re-read the same files N times.

​

Code intelligence, layered

Operations (go-to-definition, rename, diagnostics…) try the best backend first, fall back if it fails: LSP runs via Neovim when the editor is open, via standalone servers otherwise. The agent always has it.

​

System prompt

Every turn, the prompt is assembled from: mode, project info, git context, the repo map, your memory, forbidden files, active skills. The repo map is personalized per-turn — files you just edited or referenced get boosted. See repo map for ranking details, compound tools for the one-call tools, code intelligence for the backend router.