Brokentooth.io / Tags

—sessionmunch

Articles, projects and notes sharing this tag.

7 entries

  1. 01 A Memory System Should Be Able to Show Its WorkEvidence, editable Markdown, and an honest route back to the record are how I want agent memory to earn trust. Design principles#sessionmunch#provenance#local-first#open-source#agent-memory
  2. 02 How SessionMunch finds useful project memoryExact words, entities, links, and optional vectors each get a vote. The result still needs judgment. #sessionmunch#search#retrieval
  3. 03 I Got Tired of Being My AI's MemoryWhy I started building SessionMunch, and why another clever answer was less useful than remembering the last one. Founder note#sessionmunch#agent-memory#building#open-source
  4. 04 SessionMunchShared project memory for coding agents. Keep the history, recover the useful part, and stop explaining the same project from scratch. v0.1.0 release candidate#sessionmunch#agents#memory#rust#sqlite#open-source
  5. 05 SessionMunch hooks and MCP do different jobsHow capture, recall, and startup handoffs connect agents to shared memory, with the limits kept visible. #sessionmunch#mcp#integrations
  6. 06 SessionMunch without an AI summarizerWhat survives with the models switched off, and why evidence comes before interpretation. #sessionmunch#architecture#evidence
  7. 07 SessionMunch, jCodeMunch, and the Agent Memory MapCode search, documentation search, session history, and stateful agents solve different problems. Here is the distinction that shaped my choice. Architecture and comparison#sessionmunch#jcodemunch#jdocmunch#agent-memory#architecture