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.
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?
Trendoline