Show HN: Gitwhy – links AI coding sessions to Git commits before deletion
gitwhy git blame tells you who wrote the line. A safety copy of all your transcripts, because Claude Code deletes them after 30 days by default — silently, with no undo (#59248, #62476). A small memory file (GITWHY.md) your agents read at the start of each session, so they already know why the code is the way it is instead of re-discovering it every time.
- ▪gitwhy git blame tells you who wrote the line.
- ▪A safety copy of all your transcripts, because Claude Code deletes them after 30 days by default — silently, with no undo (#59248, #62476).
- ▪A small memory file (GITWHY.md) your agents read at the start of each session, so they already know why the code is the way it is instead of re-discovering it every time.
Hacker News (AI / LLM) files mainly under ai. We currently carry 2,758 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/mehrtam/gitwhy |
| Publication time | Wed, 29 Jul 2026 13:22:33 +0000 |
| Retrieval time | 2026-07-29T13:38:03.325Z |
| Last seen | 2026-07-29T13:38:03.325Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | uRyMfvH047lF · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
gitwhy git blame tells you who wrote the line. This tells you why. What is this? When you build software with AI agents (Claude Code, Codex), the reasoning — what you asked for, what the agent decided, which alternatives were rejected — lives in session transcripts on your disk. gitwhy turns those transcripts into three useful things: A visual report: click any file in your project and see the conversations that created it, in order — you asked → the agent reasoned → the commit. A safety copy of all your transcripts, because Claude Code deletes them after 30 days by default — silently, with no undo (#59248, #62476). A small memory file (GITWHY.md) your agents read at the start of each session, so they already know why the code is the way it is instead of re-discovering it every time.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.