Expand description
symforge init command — client-aware Claude/Claude Desktop/Codex/Gemini/Kilo Code configuration.
Strategy:
- Discover the absolute path of the running symforge binary.
- Configure Claude, Claude Desktop, Codex, Gemini, Kilo Code, or all based on the selected client target.
- For Claude (Code), merge symforge hook entries into
~/.claude/settings.jsonand register the MCP server in~/.claude.json. - For Claude Desktop, register the MCP server in
claude_desktop_config.json. On Windows, a.cmdwrapper is generated to fix the System32 CWD issue. - For Codex, register the MCP server in
~/.codex/config.toml. - For Kilo Code, register the MCP server in
.kilocode/mcp.json(workspace-local). - 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
settingsValue 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.jsonusing the absolute binary path. - run_
init - Entry point called by main.rs for
symforge init. - run_
init_ with_ context - Testable core for
symforge initwith injected paths. - run_
scan - Entry point for
symforge init --scan [--apply --serve-url <url> [--serve-key <key>]].