Turn Claude Code into a plan-execute-validate loop with parallel work, intelligent retry, and memory
Copy the install, test the workflow, then decide if it earns a permanent slot.
Fresh repo activity plus visible builder pull. This is the kind of tool people test before it turns obvious.
Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
GitHub health unknown. no security policy. Fresh enough repo health and manageable issue load keep the risk controlled.
AI Agent
Claude Code
Model
Claude
Fastest way to find out if forge belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
claude mcp add forge-2 -- npx forge-2Run this first. You will know quickly if the workflow earns a permanent slot.
claude mcp remove forge-2No messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude.json └─ mcp_servers/ └─ forge-2 ← registers here
Turn Claude Code into a plan-execute-validate loop with parallel work, intelligent retry, and memory