Every time I started a new Claude Code session I had to re-explain the project. Decisions made, approaches rejected, files changed, all gone. I spent the first 20 minutes of every session just rebuilding context. So I built Iranti. It’s an MCP server that Claude Code writes facts to as it works and reads from at the start of every session. One iranti claude-setup command adds it as an MCP server, and from that point forward context persists across every session reset. The cross-tool part is where it gets more useful. If you use Codex or Copilot on the same project, they connect to the same Iranti instance. What Claude Code figures out, Codex already knows when you open a new session there. AGPL, self-hosted, runs on Postgres. iranti.dev for setup instructions and the benchmarks against other memory tools. submitted by /u/PowerHouseXIV
Originally posted by u/PowerHouseXIV on r/ClaudeCode