Claude Code forgets everything between sessions. You burn tokens re-explaining your stack every time. Elephant fixes that: 🧠 Persistent memory — auto-loaded at session start. 👥 Team memory — ELEPHANT.md lives in your repo, committed, author-tagged. 🌍 Cross-repo — switch projects, keep the thread. 📝 Auto changelogs — /elephant changelog reads git log, suggests semver bump. 📖 Auto READMEs — badges and commands stay in sync. One-line install. MIT. Just a file, no cloud.

Framer — Launch websites with enterprise needs at startup speeds.

Launch websites with enterprise needs at startup speeds.

Hey PH 👋 I built Elephant because I got tired of starting every Claude Code session with the same 200-token preamble: "we use Bun not Node, auth moved to packages/core, don't touch the stripe webhook it's mid-migration..." Elephant is three files doing boring work well: • ELEPHANT.md — repo-local, committed, team-shared memory. Every entry tagged with author. • ~/.claude/elephant/memory.md — personal cross-repo memory. • CHANGELOG.md — auto-generated from git log with semver-aware bumps. A SessionStart hook loads memory automatically. A Stop hook nudges Claude to save important decisions when topics shift. Caveman-compressed entries keep a week of history at ~150 tokens. Bonus: /elephant takeover reads your last 60 commits and seeds memory on a fresh clone — new teammates get briefed before their first session. MIT. No cloud. Works today on Claude Code. Would love feedback! What's the most painful context you lose between AI coding sessions?