Home

SymForge Wiki

This wiki is the long-form reference for SymForge. The repository README is the fast product entry point. The wiki explains how the runtime, tools, supported inputs, and setup flows work after SymForge is installed.

Start here

Use the repository README for install, first-run setup, and the public product overview. Use this wiki when you need operational details, exact tool behavior, or deeper architecture.

Current Snapshot

• Rust-native local-first MCP server for AI coding agents.
• 32 MCP tools plus prompts and resources for orientation, reading, search, impact tracing, validation, indexing, checkpointing, and structural edits.
• Trust envelopes on query responses: match type, source authority, parse state, completeness, scope, and file:line evidence anchors.
• 19 source languages parsed through tree-sitter.
• Config and document indexing for JSON, TOML, YAML, dotenv/env, Markdown, and GitHub Actions workflow YAML facts.
• In-process LiveIndex is the primary read path; optional daemon mode shares state across local sessions.
• Local state lives under .symforge/, including snapshots, optional ranking stores, sidecar metadata, and optional analytics.
• npm distribution downloads prebuilt binaries for Windows x64, Linux x64, macOS arm64, and macOS x64.

Use The README For

• what SymForge is
• installing through npm
• symforge init
• CLI command overview
• current public product shape
• build and release commands

Repository README:

• README.md

Use The Wiki For

• setup prompt for agents and client rules
• architecture and data-flow details
• complete tool-family reference
• runtime, daemon, sidecar, snapshot, and local-state behavior
• supported languages and repository-intelligence formats
• environment variables and platform-specific setup snippets
• benchmark methodology and token-savings tradeoffs

Pages

Setup and configuration

• Agent-Setup-Prompt
• Environment-Setup-Scripts

Product and architecture

• Architecture-and-How-It-Works
• Runtime-Model

Tooling and capability reference

• Tool-Reference
• Supported-Languages-and-Config-Formats

Performance and tradeoffs

• Benchmarks-and-Token-Savings

Rule of thumb

Let SymForge own semantic code understanding and structural source edits. Let the shell own builds, tests, package managers, containers, and runtime process work.