From f5fffd64b810154494b7a4c0e6a1d223cdf280c1 Mon Sep 17 00:00:00 2001 From: Dave Date: Tue, 17 Mar 2026 16:17:34 +0000 Subject: [PATCH] story-kit: create 266_story_matrix_bot_structured_conversation_history --- ...rix_bot_structured_conversation_history.md | 21 +++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 .story_kit/work/1_upcoming/266_story_matrix_bot_structured_conversation_history.md diff --git a/.story_kit/work/1_upcoming/266_story_matrix_bot_structured_conversation_history.md b/.story_kit/work/1_upcoming/266_story_matrix_bot_structured_conversation_history.md new file mode 100644 index 0000000..7865d38 --- /dev/null +++ b/.story_kit/work/1_upcoming/266_story_matrix_bot_structured_conversation_history.md @@ -0,0 +1,21 @@ +--- +name: "Matrix bot structured conversation history" +--- + +# Story 266: Matrix bot structured conversation history + +## User Story + +As a user chatting with the Matrix bot, I want it to remember and own its prior responses naturally, so that conversations feel like talking to one continuous entity rather than a new instance each message. + +## Acceptance Criteria + +- [ ] Conversation history is passed as structured API messages (user/assistant turns) rather than a flattened text prefix +- [ ] Claude recognises its prior responses as its own, maintaining consistent personality across a conversation +- [ ] Per-room history survives server restarts (persisted to disk or database) +- [ ] Rolling window trimming still applies to keep context bounded +- [ ] Multi-user rooms still attribute messages to the correct sender + +## Out of Scope + +- TBD