7 ms·

Show HN: Story Keeper – AI agents with narrative continuity instead of memory

16 points by neurobloom 11mo ago

Hi HN! Creator here. I built Story Keeper to solve a problem I kept hitting with AI agents: they remember everything but lose coherence over long conversations. The Core Idea Instead of storing chat history and retrieving chunks (RAG approach), Story Keeper maintains a living narrative: Characters: Who you are (evolving), who the agent is Arc: Where you started → where you're going Themes: What matters to you Context: The thread connecting everything Think of it as the difference between reading meeting notes vs. being in the relationship. Technical Approach ~200 lines of Python. Three primitives: Story State (not message list) Story Evolution (not appending) Story-Grounded Response (not retrieval) Works with any LLM - tested with GPT-4, Claude, Llama 3.1, Mistral. Why This Works Traditional memory is about facts. Story Keeper is about continuity. Example: Health coaching agent Normal: Generic advice each time Story Keeper: "This is the pattern we identified last month. You do better with 'good enough' than perfect." The agent carries forward understanding, not just data. Implementation Part of PACT-AX (open source agent collaboration framework). MIT licensed. Simple integration: pythonfrom pact_ax.primitives.story_keeper import StoryKeeper keeper = StoryKeeper(agent_id="my-agent") response = keeper.process_turn(user_message) Use Cases I'm Exploring Long-term coaching/mentorship Multi-session research assistants Customer support with relationship continuity Educational tutors that understand learning journeys What I'd Love Feedback On Is this solving a real problem or am I overthinking it? Performance concerns at scale? Other approaches people have tried for this? Use cases I'm missing? The full technical writeup is in the repo blog folder. Happy to answer questions!

deleted 11mo ago
[deleted]
neurobloom 11mo ago
[dead]
nvdnadj92 11mo ago
After reading this post and the readme, I'm not convinced that this is solving a real, observed problem. You outline an example with the long-term coaching mentorship, but why or how is your solution preferable to telling Claude to maintain a set of notes and observations about you, similar to https://github.com/heyitsnoah/claudesidian https://github.com/heyitsnoah/claudesidian? the jazz metaphors do not help provide additional context.
- neurobloom 10mo ago
  Fair feedback. Claudesidian is a productivity system where you organize knowledge and Claude assists. StoryKeeper is relational infrastructure that maintains emotional continuity across AI sessions and agent handoffs. Different layers of the stack, both valuable. I'll update the docs to make this clearer — appreciate the push for concreteness.
R_D_Olivaw 11mo ago
I just finished watching the Animatrix, so forgive me if this is slightly off but, This strikes me as precisely how we get ai companies that will build, run, and market themselves all while maintaining a consistent "narrative brand arc" that makes us root for them. I do see your usage cases, but would probably do better in Saleslandia packaged and narrowed down for each particular niche. I'm curious of this might be beneficial to Writers/world builders.
- neurobloom 10mo ago
  You're seeing something real in all three observations: AI narrative consistency: Yes, this is infrastructure for maintaining coherent identity over time — whether human ↔ AI or AI-agent organizations. Niche packaging: Agreed. While the core is general infrastructure, entry strategy should be vertical-specific (customer support, coaching, education, etc.) Writers/world-builders: Great callout. Character consistency across long narratives is exactly the kind of "emotional continuity" problem StoryKeeper addresses. The broader vision is relational infrastructure for AI systems. The go-to-market is specific solutions for specific communities. Writers might be a great early adopter group

16 points by neurobloom 11mo ago

deleted 11mo ago

[deleted]

neurobloom 11mo ago

[dead]

nvdnadj92 11mo ago

After reading this post and the readme, I'm not convinced that this is solving a real, observed problem. You outline an example with the long-term coaching mentorship, but why or how is your solution preferable to telling Claude to maintain a set of notes and observations about you, similar to https://github.com/heyitsnoah/claudesidian https://github.com/heyitsnoah/claudesidian? the jazz metaphors do not help provide additional context.

neurobloom 10mo ago
Fair feedback. Claudesidian is a productivity system where you organize knowledge and Claude assists. StoryKeeper is relational infrastructure that maintains emotional continuity across AI sessions and agent handoffs. Different layers of the stack, both valuable. I'll update the docs to make this clearer — appreciate the push for concreteness.

R_D_Olivaw 11mo ago

I just finished watching the Animatrix, so forgive me if this is slightly off but, This strikes me as precisely how we get ai companies that will build, run, and market themselves all while maintaining a consistent "narrative brand arc" that makes us root for them. I do see your usage cases, but would probably do better in Saleslandia packaged and narrowed down for each particular niche. I'm curious of this might be beneficial to Writers/world builders.

neurobloom 10mo ago
You're seeing something real in all three observations: AI narrative consistency: Yes, this is infrastructure for maintaining coherent identity over time — whether human ↔ AI or AI-agent organizations. Niche packaging: Agreed. While the core is general infrastructure, entry strategy should be vertical-specific (customer support, coaching, education, etc.) Writers/world-builders: Great callout. Character consistency across long narratives is exactly the kind of "emotional continuity" problem StoryKeeper addresses. The broader vision is relational infrastructure for AI systems. The go-to-market is specific solutions for specific communities. Writers might be a great early adopter group