Skip to main content

Module init

Module init 

Source
Expand description

symforge init command — client-aware Claude/Claude Desktop/Codex/Gemini/Kilo Code configuration.

Strategy:

  1. Discover the absolute path of the running symforge binary.
  2. Configure Claude, Claude Desktop, Codex, Gemini, Kilo Code, or all based on the selected client target.
  3. For Claude (Code), merge symforge hook entries into ~/.claude/settings.json and register the MCP server in ~/.claude.json.
  4. For Claude Desktop, register the MCP server in claude_desktop_config.json. On Windows, a .cmd wrapper is generated to fix the System32 CWD issue.
  5. For Codex, register the MCP server in ~/.codex/config.toml.
  6. For Kilo Code, register the MCP server in .kilocode/mcp.json (workspace-local).
  7. Create .symforge/ in the current working directory (runtime needs it).

Identification: any hook entry whose hooks[].command contains the substring "symforge hook" is considered a symforge-owned entry and will be replaced.

Functions§

merge_hooks_into_settings
Merge symforge hook entries into settings_path, creating it if necessary.
merge_symforge_hooks
Merge symforge hook entries into an existing settings Value in-place.
register_claude_desktop_mcp_server
Register symforge as an MCP server in Claude Desktop’s claude_desktop_config.json.
register_codex_mcp_server
Register symforge as an MCP server in ~/.codex/config.toml.
register_cursor_mcp_server
Register symforge as an MCP server in Cursor’s global ~/.cursor/mcp.json.
register_gemini_mcp_server
Register symforge as an MCP server in ~/.gemini/settings.json.
register_kilo_mcp_server
Register symforge as an MCP server in .kilocode/mcp.json (workspace-local).
register_mcp_server
Register symforge as an MCP server in ~/.claude.json using the absolute binary path.
run_init
Entry point called by main.rs for symforge init.
run_init_with_context
Testable core for symforge init with injected paths.
run_scan
Entry point for symforge init --scan [--apply --serve-url <url> [--serve-key <key>]].