MemHub is a claimed 'persistent shared memory' layer for AI coding agents — attributed via echo testimony to a maker called Simplex — asserting that project decisions, corrections and constraints survive across Claude Code, Cursor, Codex, Windsurf and Cline sessions. The supplied web results do not mention MemHub at all; they show only that the shared-agent-memory category is crowded and actively marketed (mem0, Forgetful, MemU, TencentDB Agent Memory, Membase), with vendors converging on 'memory layers' as the durability/lock-in story for agents. Nothing in the supplied material establishes a MemHub release, inspectable implementation, or cross-tool interoperability test, so MemHub specifically remains an unvalidated landing-page claim within a well-evidenced category.
2026-09-25T00:17:01Z
The trigger is a repeat category builder's adjacent Show HN at 1 point / 0 comments — a fourth week of identical category noise, nothing MemHub-specific. Closing absorbed: the case's durable finding (cross-agent shared-memory demand is real and heavily built-for) is established via independent demand reports and a crowded implementation field, and is already carried by Scott's canon and sibling radar cases; MemHub itself remains an unvalidated landing-page claim with zero follow-through in ~3.5 weeks, and a genuine release would surface as a fresh episode.
2026-09-24T23:33:56Z
evidence attached: hn.story.49837643 — shared external link with case evidence
2026-09-24T01:35:19Z
grounded: known/low — MemHub restates the external, tool-independent memory position Scott's own wikis already hold — wiki-is-the-kernel and long-running-agents (durable state outsid
2026-09-24T01:32:22Z
The agency post is the clearest first-party demand signal yet — a real team running ~30 Claude Code agents hit the exact cross-agent memory-silo problem — so the category's pain is now beyond doubt. But it is one more demand anecdote, not MemHub evidence: no inspectable release, no cross-tool recall test, no interoperability result has surfaced in three weeks, and measured velocity is near zero.
2026-09-24T00:31:35Z
evidence attached: reddit.post.1wok7u6 — Independent demand evidence: an agency running ~30 Claude Code agents hit exactly the cross-agent shared-memory silo problem the case tracks.
2026-09-21T22:43:06Z
Praxos extends neighboring shared-context activity into team messaging for people and agents, but its founder's announcement provides no validation of MemHub or demonstrated portability between coding tools. This modest category expansion does not change the product-specific assessment or earn additional attention from Scott.
2026-09-21T22:23:12Z
evidence attached: hn.story.49793831 — Praxos is relevant evidence for persistent shared context across people and agents, though it is broader than coding workflows.
2026-09-21T15:48:46Z
The latest Show HN adds a neighboring shared-memory announcement, but its title alone establishes neither an inspectable implementation nor successful cross-agent context transfer. Category participation continues to broaden modestly; it does not corroborate MemHub or change its value to Scott.
2026-09-21T13:22:10Z
evidence attached: hn.story.49786875 — Independent corroboration of the open shared-memory pattern for coordinating coding agents across teams and sessions.
2026-09-20T15:34:07Z
Nimrod adds another builder's cross-agent memory claim, but the supplied excerpt contains neither an inspectable implementation nor a demonstrated transfer of context. This modest expansion of neighboring projects does not corroborate MemHub or establish a new reason for Scott to investigate it.
2026-09-20T15:22:21Z
evidence attached: reddit.post.1wlj0uq — This is a concrete local artifact supporting the open hypothesis that shared memory can transfer project context across coding-agent harnesses.
2026-09-16T19:30:15Z
The new Cortex and Friday titles add neighboring memory-layer announcements, not implementation results or independent validation of MemHub. Their attachment rationales overstate what the supplied evidence establishes; MemHub remains an unvalidated product claim rather than a development that changes Scott's building decisions.
2026-09-16T19:22:34Z
evidence attached: hn.story.49731353 — This independent released MCP implementation supports the same developing pattern of self-hosted persistent memory for coding agents.
2026-09-16T19:22:34Z
evidence attached: hn.story.49731631 — Another released agent state and memory layer materially contextualizes the open question of portable persistence across autonomous agents.
2026-09-15T15:33:04Z
Make0 AI adds another builder's account of wanting continuity when switching between Claude Code and Codex, not evidence that MemHub provides it. The supplied excerpt does not establish the local-memory or retrieval implementation described in the attachment rationale; this remains repeated category demand rather than product validation.
2026-09-15T15:22:44Z
evidence attached: hn.story.49713789 — A second project reports cross-agent local memory with retrieval to control context growth, materially contextualising the shared coding-agent memory hypothesis.
2026-09-14T14:30:44Z
The new Show HN title announces another coding-agent memory plugin, but supplies neither implementation details nor results and does not corroborate MemHub. This is additional category activity, not evidence that MemHub delivers portable shared context.
2026-09-14T14:22:22Z
evidence attached: hn.story.49696455 — This is an independent released coding-agent memory plugin that materially bears on whether persistent project and conversation memory is becoming practical.
2026-09-13T04:21:56Z
The new report distinguishes one-time memory migration from ongoing synchronization, but its claimed MCP-based solution is Vilix AI, not MemHub. It reinforces an already-established need without validating MemHub’s implementation or changing its value to Scott.
2026-09-13T04:21:16Z
evidence attached: reddit.post.1wexfeu — The report offers user evidence for cross-agent memory demand and shows that export-based migration does not solve ongoing synchronization.
2026-09-12T20:29:27Z
The open-source, no-signup and no-data-collection statements are ChatPanel author claims, not evidence about MemHub’s availability or privacy. This is neighboring product discussion rather than validation of shared-memory continuity, so MemHub’s assessment remains unchanged.
2026-09-11T19:35:55Z
Cartographer adds a neighboring claim about team-shared knowledge and Claude Code configuration, not evidence that MemHub preserves context across agents. The supplied excerpt does not substantiate the attachment rationale’s release or cross-tool portability claims, so this remains category activity rather than a change in MemHub’s assessment.
2026-09-11T19:22:13Z
evidence attached: reddit.post.1wdonmt — The released Cartographer artifact materially bears on shared coding-agent memory, configuration portability, and collaboration across tools.
2026-09-11T17:38:25Z
Contextify’s author now supplies concrete implementation detail—local SQLite indexing of Claude Code and Codex sessions—rather than only an announcement title. This strengthens the neighboring cross-tool history story, but does not validate MemHub or demonstrate that agents consume and preserve shared project knowledge.
2026-09-10T00:25:47Z
Contextify adds an announced Windows history index spanning Claude Code and Codex, but indexing multiple tools’ histories is not demonstrated shared-memory continuity. The title-only evidence neither validates MemHub nor establishes a workflow improvement that changes Scott’s existing approach.
2026-09-09T19:23:23Z
evidence attached: hn.story.49631979 — A live history index for Claude Code and Codex is directly relevant to portable context and memory across coding-agent sessions.
2026-09-09T10:24:50Z
Numen adds another announced external-context implementation, but its title-only evidence neither demonstrates differentiated engineering nor tests MemHub’s shared cross-agent continuity. The category continues to attract builders while this product-specific hypothesis remains unvalidated; further review should prioritize direct MemHub evidence over neighboring announcements.
2026-09-09T10:22:41Z
evidence attached: hn.story.49624069 — A self-hosted context graph over work tools is a relevant independent artifact for evaluating portable shared agent memory.
2026-09-07T14:36:45Z
Silo adds another neighboring project-memory tool, but the supplied title alone establishes neither differentiated capability nor validation of MemHub’s shared cross-agent context. This remains an untested product-specific claim within a familiar category; further review should prioritize direct MemHub implementation or interoperability evidence.
2026-09-07T14:23:11Z
evidence attached: hn.story.49598496 — A released local project database for agents materially bears on portable, persistent coding-agent memory.
2026-09-06T11:26:39Z
Refreshed neighboring-plugin comments offer anecdotal task-capture benefits and simpler scratchpad alternatives, not tested shared-memory results. MemHub’s cross-agent continuity remains unvalidated; repetitive category discussion adds no reason to advance this product-specific case.
2026-09-05T20:24:17Z
ChatPanel adds a distinct browser-to-agent context implementation and an announced Firefox expansion, not validation of MemHub’s shared-memory claims. The category continues to attract builders, but MemHub’s interoperability and implementation quality remain untested; neighboring releases should not advance this product-specific case.
2026-09-05T20:22:39Z
evidence attached: hn.story.49579835 — A second implementation combines persistent notes and meeting context with an MCP bridge for cross-agent retrieval, materially contextualizing shared coding-agent memory.
2026-09-05T17:29:47Z
Refreshed project-memory comments add an anecdotal SQL/MCP workaround, reinforcing demand for external memory without testing MemHub. Its shared cross-agent continuity remains unvalidated; neighboring implementations and discussion do not advance this product-specific case.
2026-09-05T14:26:02Z
The refreshed neighboring-plugin discussion adds no substantive evidence about MemHub or shared cross-agent continuity. MemHub remains an unvalidated product-specific claim; adjacent memory-tool commentary does not warrant promotion or renewed attention.
2026-09-05T13:27:53Z
The neighboring plugin discussion remains repetitive, with backlogs and Markdown files offered as simpler alternatives rather than new implementation evidence. Nothing advances MemHub’s claimed shared cross-agent continuity; further hourly reviews of these adjacent discussions are unlikely to add value.
2026-09-05T12:24:29Z
The refreshed neighboring-plugin discussion adds no substantive validation; its automated consensus summary is not independent user evidence. MemHub’s cross-agent continuity remains an untested product claim, and category discussion does not advance this case.
2026-09-05T10:28:26Z
Refreshed neighboring-tool discussions emphasize selective recall, decision-specific aging, and simpler task tracking, but provide recommendations rather than measured results. They do not advance MemHub’s product-specific claim of shared cross-agent continuity or change its value to Scott.
2026-09-05T09:26:01Z
The refreshed discussion adds a bounded-scratchpad recommendation and cautions about memory errors, not tested results or new interoperability evidence. These remain neighboring-tool design observations; MemHub’s shared-context claim is still unvalidated.
2026-09-05T08:27:12Z
Refreshed claude-adhd comments add anecdotal support for capturing forgotten work before sessions end, but no tested improvement or cross-agent continuity evidence. MemHub remains an unvalidated product claim within an established category; discussion of neighboring tools does not advance its maturity.
2026-09-05T07:23:42Z
Cortex adds concrete author-reported lifecycle capture and token-budgeted retrieval, while claude-adhd and shared-repository workarounds reinforce demand for external memory. These corroborate the category, not MemHub’s shared cross-agent continuity; correcting the inherited maturity to watching keeps this product-specific case from borrowing validation from unrelated implementations.
2026-09-05T07:22:26Z
evidence attached: reddit.post.1w7szdx — Independent first-party artifact directly corroborates the episode around local, persistent memory shared across coding-agent sessions.
2026-09-05T07:22:26Z
evidence attached: reddit.post.1w7tb2v — A released local plugin is an additional implementation of persistent, cross-session memory for coding agents.
2026-09-04T14:34:18Z
The refreshed Engram discussion adds only a naming comparison to an academic paper, not evidence of adoption, implementation quality, or cross-agent interoperability. The category remains corroborated by multiple implementations, while MemHub’s specific claims remain unvalidated.
2026-09-04T02:29:09Z
Refreshed comments sharpen the architectural tradeoff: project isolation is intentional, while practitioners externalize reusable knowledge into shared folders, skills, and documentation. This reinforces the category and Scott’s existing approach but still provides no validation of MemHub’s portability, provenance, permissions, or implementation quality.
2026-09-04T00:28:04Z
The user report further confirms the practical cross-project continuity gap and file-based workarounds, strengthening demand for this category. It does not test MemHub or reduce uncertainty around interoperability, provenance, permissions, or implementation quality.
2026-09-04T00:22:34Z
evidence attached: reddit.post.1w6ntm6 — A user report that Claude memories remain project-scoped provides practical counterevidence about portability and shared context across coding projects.
2026-09-03T21:40:20Z
Engram becomes a second independent implementation alongside Mex, corroborating that builders are converging on portable team memory for coding agents. This validates the category’s momentum, not MemHub’s interoperability or quality; provenance, permissions, and real cross-agent continuity remain untested.
2026-09-03T17:24:36Z
evidence attached: hn.story.49552882 — Engram's released MCP runbook memory materially contextualizes the open question of portable shared memory across coding agents.
2026-09-03T09:29:17Z
Mex 0.8.0 adds a separate implementation pursuing team memory for coding agents, strengthening evidence that builders see the same coordination gap. It still provides no independent validation of MemHub, demonstrated cross-agent portability, or evidence that either implementation solves provenance and permissions well.
2026-09-03T09:22:15Z
evidence attached: hn.story.49547372 — Released team-memory tooling directly bears on whether shared context becomes portable across coding agents, though the low-engagement post provides no independent validation.
2026-09-03T07:30:09Z
Independent user evidence strengthens the demand-side case for team-wide memory beyond individual accounts, but it does not validate MemHub’s implementation or claimed cross-agent portability. The case is now worth watching as a possible solution to a real gap, not treating as corroborated capability.
2026-09-03T07:21:51Z
evidence attached: reddit.post.1w5zyle — Direct user evidence that per-account memory and shared projects leave a practical gap for team-wide coding-agent continuity.
2026-09-03T02:38:29Z
No new evidence establishes implementation quality or cross-agent interoperability; the case remains an unvalidated instance of an already well-covered memory pattern.
2026-09-03T02:36:44Z
grounded: known/low — MemHub repeats the external, tool-independent memory position already held in “Wiki Is the Kernel,” “Long-Running Agents,” and Scott’s dev-wiki implementation;
2026-09-03T02:34:28Z
origin walked (codex/luna, conf 0.96): anchor hn.story.49544996 -> echo.other.f457837463 by MemHub by Simplex
2026-09-03T02:32:44Z
case created — MemHub is a distinct persistent-memory artifact rather than evidence about the already tracked OpenContext product.