M8M – See what your AI remembers about you and detect memory poisoning
m8m AI memory observability, provenance & security. Nothing gets past. m8m monitors what your AI agents remember about you — where each memory came from, what changed, and whether anything looks suspicious. Your AI remembers everything about you — preferences, habits, work patterns, relationships.
- ▪m8m AI memory observability, provenance & security.
- ▪Nothing gets past. m8m monitors what your AI agents remember about you — where each memory came from, what changed, and whether anything looks suspicious.
- ▪Your AI remembers everything about you — preferences, habits, work patterns, relationships.
Hacker News (AI / LLM) files mainly under ai. We currently carry 5,325 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/th0t3p/m8m |
| Publication time | Thu, 17 Sep 2026 13:20:55 +0000 |
| Retrieval time | 2026-09-17T13:23:44.844Z |
| Last seen | 2026-09-17T13:23:44.844Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | eh0bDoQrZH0e · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
m8m AI memory observability, provenance & security. Eight eyes. Nothing gets past. m8m monitors what your AI agents remember about you — where each memory came from, what changed, and whether anything looks suspicious. The core pieces share one local SQLite database: MCP server — live memory operations as your agent works File watcher — tracks local memory files (MEMORY.md, CLAUDE.md, …); it runs automatically inside the MCP server (and can also run standalone via m8m watch) Security analysis — pattern-based scanning of every memory for credentials, instructions, URLs/emails, and hidden characters Snapshots & rollback — point-in-time baselines to diff drift and roll back CLI — query and audit memory state from the terminal Local dashboard — a dark, browser-based visualization Phase 1 is…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.