Sight across repos, not just one.
Forge is metalmind's cross-repo code graph. HTTP-route edges connect a caller in service A to its handler in service B — across language, framework, and repo boundaries — with provenance Claude can trust-grade.
Three edge tiers
OpenAPI specs on the metalmind shelf (never inside your repos), Java RestTemplate / WebClient / Feign callers, and URL string literals as an opt-in fallback. Each edge carries INFERRED_NAME, INFERRED_ROUTE, and INFERRED_URL_LITERAL provenance.
Symbol-aware navigation
symbolburn iron returns a symbol's neighbors — who calls it, what it calls, its module. renameburn steel drives a coordinated rename through Serena's LSP backend, across every repo in the forge.
Team-debug, primed
debugburn zinc hands a bug to the /team-debug skill with the code graph already loaded. The team agents start with context, not cold.
One query. Two repos. One answer.
A caller in billing-svc; a handler in notif-svc. Native Claude has no concept of "the other service's code." Forge does.
Every inferred edge carries provenance.
Pulled from your ~/.metalmind/specs/ shelf. Routes match exactly; types are checked.
Java RestTemplate, WebClient, Feign clients with annotated routes. Strong enough for navigation; verify before refactor.
String-literal URL matching as a last resort. Off by default; surfaces with explicit INFERRED_URL_LITERAL grade.