Install¶
Requirements¶
- Python ≥ 3.10 (3.10, 3.11, 3.12, 3.13 all tested via CI matrix)
- Claude Code CLI installed and authenticated
- macOS, Linux, or Windows
- (optional) API key for Anthropic, OpenAI, or a local Ollama daemon — without one, triforge works in dense-only mode
Recommended: pipx¶
pipx keeps triforge isolated from your project venvs:
What triforge install does:
- Patches
~/.claude.jsonto register three MCP servers (idempotent — re-running won't duplicate; preserves any user-added servers). - Writes
~/.claude/commands/rag.md(the/ragslash-command body). - Appends a short section to
~/.claude/CLAUDE.mdso every Claude session knows the three MCPs are available.
Alternative: pip¶
Optional extras¶
# Enable summary/OpenIE/cleaner via cloud LLMs:
pipx install 'triforge[llm]'
# Add the InsForge migrate target:
pipx install 'triforge[insforge]'
# Build docs locally:
pipx install 'triforge[docs]'
Per-project activation¶
Inside any project folder, run:
(in a Claude Code session). This invokes the slash-command body — Claude executes triforge install --project-only --here, which writes:
.triforge/config.json— the marker file (default storagelocal, no exclude patterns)..triforge/.gitignore— so the marker dir never leaks into the project's git history..claude/settings.local.json— three hooks (SessionStart,Stop,SessionEnd) bound to the absolute path of thetriforgebinary.- A
## Triforge memorysection appended toAGENTS.md(orCLAUDE.mdifAGENTS.mdis absent).
From the next chat onward, capture/index/retrieve happens automatically.
Verify¶
Uninstall¶
triforge uninstall # removes our MCP entries from ~/.claude.json + the slash-command file
pipx uninstall triforge
To wipe a single project's memory:
Per-project marker files (.triforge/, .claude/settings.local.json) stay in the project tree — delete them manually if you want to fully detach.