free-claude-code vs MemPalace

free-claude-code is an open-source proxy that sits between Claude Code CLI and a rotating pool of free or self-hosted LLM providers — letting anyone run Anthropic's flagship coding agent without a paid API key. The project speaks the Anthropic SSE format natively and also supports OpenAI chat SSE, so it works transparently with both the Claude Code terminal and the official VSCode extension. The proxy runs on :8082 and routes requests to NVIDIA NIM (40 rpm free tier), OpenRouter free models, LM Studio, llama.cpp, or Ollama — whatever you configure. The Discord integration is the most novel bit: you can send coding tasks from any Discord server, watch live streaming output, and manage multiple concurrent agent sessions remotely. The project hit 13,500 GitHub stars within days of trending, making it one of the fastest-rising repositories in April 2026. The ethical angle is murky — it works by routing around Anthropic's billing — but the technical execution is clean. It's essentially a developer-grade proxy with multi-provider failover and a slick Discord UI bolted on. For teams who want to experiment with agentic coding workflows before committing to API costs, it's a useful sandbox.

MemPalace is a free, MIT-licensed AI memory framework that stores LLM conversation data verbatim locally — no AI summarization step, no per-query API costs. It integrates with Claude Code, ChatGPT, and Cursor via MCP, and claims the highest LongMemEval benchmark score among free memory frameworks at 96.6% (initially claimed 100% before community pressure forced a correction after GitHub issue #29 exposed test-set tuning). The project went viral on GitHub with 23,000+ stars in under 48 hours, partly because it was built by actress Milla Jovovich and developer Ben Sigman — an unusual origin story that dominated early coverage. But the technical pitch is real: competing paid solutions (Mem0 at $19–249/month, Zep at $25+/month) do similar things and charge for the privilege. MemPalace runs fully local, connects to any POSIX filesystem, and the verbatim storage approach avoids hallucination artifacts introduced by AI-summarized memory. The catch: verbatim storage means much higher storage overhead than summarization-based approaches, retrieval latency grows with context size, and the benchmark controversy raised questions about the team's methodology. For personal projects and small teams, the zero-cost angle is hard to argue with. For production systems where memory quality is critical, wait for independent benchmarking.