Building a meeting-prep agent with real memory in ~60 lines: Hindsight + Groq
UmeshGupta2008 · reddit · 2026-11-07
A first-year AI/ML student shares how they built a meeting prep & action-item agent in 60 lines of code, addressing LLMs' statelessness.
Core idea: stop stuffing context, start recalling it
- Instead of dumping all past notes into the prompt (expensive, slow, noisy), split into two verbs:
- Retain: store notes in Hindsight's long-term memory;
- Recall: fetch only relevant memories when asked.
- Architecture is deliberately boring: input → router → [retain] or [recall + Groq inference] → response, all inside a while True loop; question detection uses simple keyword triggers (prep/what/who/when/remind/?).
- No vector DB config, embedding pipeline, or chunking strategy—memory is Hindsight's job; reasoning runs on llama-3.3-70b-versatile via Groq.
In practice: after meetings, type notes like "John promised slides by Thursday"; before the next call, type "Prep me for my meeting with John" and the agent returns open commitments, relevant decisions, and a suggested opener.
The author's takeaway: memory turns a stateless chatbot into a collaborator that accumulates a relationship with your work.
Related event: Developers Build Ever-Remembering Meeting Agent with Hindsight(2 posts)→
More from coding & agent
- herdr desktop app embeds real libghostty terminals so you never leave the terminal — solyarisoftware · 2026-11-07
- Omnigraph: open-source graph database with git-style branching for multi-agent shared memory — solyarisoftware · 2026-11-07
- Devin desktop UI redesign preview leaks: 880 ACU usage, 380 PRs merged — ghumare64 · 2026-11-07
- hmcp-gateway: default-deny MCP gateway that holds every write or delete for human approval — Aoutix · 2026-11-07
- Problem #4 of running 100 AI agents: cascading failures and runaway retries — goyalshaliniuk · 2026-11-07
- Problem #5 of running 100 AI agents: observability, security and per-agent cost tracking — goyalshaliniuk · 2026-11-07