Show HN: EchoChain to see what happens when LLMs play telephone
Hey HN Community! I created `echoChain` to explore the following phenomenon: how much data retained after LLMs exchange responses multiple times? Imagine the game of telephone but with AIs. Each model converts the response into a question, which is then answered. After several rounds, facts get mutated, details get stripped, and the answer is far removed from the initial one. `echoChain` is an OSS Python CLI that helps measure this process. It allows for multi-model testing, model rotation, trac
Read original source
Source record
Recorded metrics
points · 2 votes
2026-11-02 11:00:28.768Z
cumulative since publication
Research analysis
Project record
Repository: smusali/echoChain. Source account: Hey HN Community! I created `echoChain` to explore the following phenomenon: how much data retained after LLMs exchange responses multiple times? Imagine the game of telephone but with AIs. Each model converts the response into a question, which is then answered. After several rounds, facts get mutated, details get stripped, and the answer is far removed from the initial one. `echoChain` is an OSS Python CLI that helps measure this process. It allows for multi-model testing, model rotation, trac
Observed adoption & comparisons
Source votes: 2 votes (Nov 2, 2026 UTC; cumulative since publication); previous same-scope observation: 1 (Nov 2, 2026 UTC). These observations do not establish demand growth. Recent records to compare: “Memorilla: Latent Semantic Memory for LLMs” (Hacker News, Nov 6, 2026); “Blender's UI and Runtime: Much Faster Than GPUI” (Hacker News, Nov 6, 2026). Shared themes are navigation hints; they have not been verified as the same need or independent corroboration.
Adoption decision
Evaluate it against the tool or manual workflow it would replace. The stored record supports discovery; it does not yet establish reliability, lower operating cost or commercial adoption.
Unverified requirements
Not verified: license permissions, required hardware, installation steps, maintenance status and a representative task with its failure cases.
Next test
Choose one real task and a current alternative. Record the commit, environment, input, output, elapsed time and failure behavior; retain the result before recommending adoption.