diff --git a/hindsight-docs/blog/2026-04-21-hindsight-10k-stars.md b/hindsight-docs/blog/2026-04-21-hindsight-10k-stars.md index 1fc793ee20..d6330fdbd1 100644 --- a/hindsight-docs/blog/2026-04-21-hindsight-10k-stars.md +++ b/hindsight-docs/blog/2026-04-21-hindsight-10k-stars.md @@ -17,6 +17,8 @@ That vote of confidence came from real deployments. Moreover, it came from teams Today, we're celebrating that community and sharing what the numbers reveal about Hindsight's impact. Here's the story behind 10,000 stars, what surprised us most, and where agent memory systems are headed. + + --- ## By the Numbers diff --git a/hindsight-docs/blog/2026-06-08-oh-my-pi-hindsight-memory.md b/hindsight-docs/blog/2026-06-08-oh-my-pi-hindsight-memory.md index f43de86ef8..2c84ea8230 100644 --- a/hindsight-docs/blog/2026-06-08-oh-my-pi-hindsight-memory.md +++ b/hindsight-docs/blog/2026-06-08-oh-my-pi-hindsight-memory.md @@ -15,6 +15,8 @@ hide_table_of_contents: true It's not a thin integration either: it features a complete memory subsystem built on top of Hindsight's API — bank scoping, mental-model seeding, debounced retain queues, auto-recall on the first turn. This post is a tour of how they built it, with code pulled straight from the public repo. If you're considering Hindsight for a coding agent of your own, this is a useful reference for the shape of a deep integration. + + ## TL;DR - oh-my-pi exposes `retain` / `recall` / `reflect` as model-facing tools backed by Hindsight, plus an auto-retain / auto-recall lifecycle the model doesn't have to think about.