symforge 8.14.0

SymForge — in-memory code intelligence MCP server for Claude Code, Codex, and Gemini CLI
Documentation
1
2
3
4
5
6
7
8
9
10
11
# Lessons

- 2026-07-10: For SymForge repository work, use the full SymForge MCP surface for code inspection and editing after a fresh `index_folder` plus `checkpoint_now(verify_after_write=true)`. If the connector is compact or unbound, report that limitation and repair/reconnect it; never silently fall back to `Get-Content`, Read, Grep, or Glob. Use direct reads only for exact docs/configs or after an explicit SymForge failure.
- 2026-07-10: Run and monitor long or noisy commands such as Cargo builds/tests through Terminal Commander with structured rules and bounded summaries. Never stream raw build logs through repeated terminal polling; report only matched failures and the final exit verdict.
- 2026-07-10: Delegated code tasks must include the full-surface SymForge helper path (`.symforge/codex-mcp-call.ps1 -UseRelease`). A compact or unbound registered connector is not permission for a subagent to inspect source through Terminal Commander or raw file tools; re-run any fallback inspection through SymForge before editing.
- 2026-07-10: In a shared worktree, serialize TDD slices that introduce compile-red tests. An unrelated missing symbol prevents every other focused Cargo test from reaching its test body. Use one compile-red slice at a time (or an isolated worktree), restore a compiling tree, then release the next Cargo gate.
- 2026-07-10: Do not use the Codex delegated-agent harness on this Windows workspace unless every worker is headless, lifecycle-bounded, and verified to leave zero child processes. Completed subagents leaked MCP/runtime sets that repeatedly opened Git terminal windows, stole desktop focus, and prevented user input. Prefer local execution; after any approved delegation, audit and terminate the worker tree before continuing.
- 2026-07-10: Route every shell, Cargo, process-inspection, and process-cleanup operation through the updated Terminal Commander. Do not call direct terminal execution even for small diagnostics; use bounded structured receipts so commands stay headless and cannot spawn focus-stealing windows.
- 2026-07-11: NEVER let library tests reach `spawn_daemon_process`/`ensure_daemon_running`'s spawn path. Under `cargo test`, `current_exe()` is the libtest binary and the `daemon` argument is a TEST FILTER, so auto-spawn re-runs the daemon test subset recursively — an exponential fork bomb that floods the desktop with console windows, steals focus, and makes the machine unusable (2026-07-11 incident; the user had to kill everything). The daemon now refuses to auto-spawn from a test build (cfg(test)), from any Cargo `deps/` artifact (by path), and when `SYMFORGE_DAEMON_AUTOSPAWN=off`; any future code that spawns `current_exe()` must carry the same three guards, and any test that can reach a reconnect/spawn seam must prove the guard holds before running the suite.
- 2026-07-11: Windows self-update DESIGN DECISION (user-set): `symforge update` terminating every same-install-path holder (including other harnesses' live MCP stdio transports) is INTENDED behavior, not a defect. The user prefers killing verified same-install lock holders and manually reconnecting SymForge in each harness over a copy-on-write/rename-aside swap that leaves old renamed images running. A rename-aside implementation was built and then reverted on the user's explicit call (2026-07-11); do not re-propose it. Ownership boundary: SymForge kills verified same-path holders + re-registers configs; the harness/user reconnects sessions.
- 2026-07-11: The embed gate is `cargo test --no-default-features --features embed --lib` (CI's exact command), NOT `cargo check --features embed` — check skips cfg(test) code, so an embed-visible TEST module calling a server-gated helper (process_util) passed check locally and failed CI. Always run the CI job's verbatim command before claiming a gate green.