MemTether's author (Emotional-Sky9692) claims his released local-first hub lets 23 coding agents — Claude Code, Cursor, Windsurf, Codex, and others — share one SQLite memory file through junction/symlink pointers, with attribution, bi-temporal records, and MCP support and no cloud or server; real adoption by multi-agent users would establish file-pointer shared memory as a practical cross-agent memory substrate.
state: seedheat: lowuncertainty: mediumconvergesscott: mediumagent-memory cross-agent-shared-memory local-first-infrastructure
What is this?
MemTether is a released local-first tool by indie developer 'Emotional-Sky9692' claiming to let ~23 AI coding agents (Claude Code, Cursor, Windsurf, Codex among them) share one SQLite memory file via filesystem junction/symlink pointers, with per-agent attribution, bi-temporal records, and MCP support — no cloud, no server. The supplied search results do not surface MemTether or its author directly, so its specific claims and any real adoption remain unverified from this evidence. What the results do establish is that the surrounding territory is crowded and fast-moving: projectmem (local-first `.projectmem/` memory directory for Claude Code/Cursor/Codex via MCP stdio, explicitly no cloud), Redthread (git-backed portable agent memory), agent-shadow-brain ('one open-source brain' shared across Claude Code, Cursor, Cline, Codex, Copilot, Windsurf), VEKTOR (SQLite-first local agent memory, paid), mem0 (66K+ star memory layer with maintained Claude and Codex plugins), and memtrace (codebase-as-knowledge-graph memory). MemTether's distinguishing bet — a single SQLite file shared across agents by OS-level file pointers rather than a directory convention or a service — is exactly the thing the snippets neither confirm nor refute.
Why it matters to Scott
Independently arrives at Scott's shared-blackboard / durability-beats-coordination position — one durable external medium that replaceable coding agents all read and write with attribution — but bets against his Markdown OS inspectability doctrine by sharing an opaque SQLite file via OS junctions/symlinks instead of a plain-text folder, making it a falsifiable rival substrate on exactly the legible-wiki-graph vs machine-native-file question his three-substrates framework adjudicates. If the 23-concurrent-writers claim survives (SQLite locking and attribution integrity over junction pointers being the failure points his deterministic control plane work predicts), it becomes a zero-server shared-memory mechanism directly relevant to OpenClaw's shared graph memory and his own Claude Code/Codex multi-agent setup; until then it is one more unverified sibling in a crowded radar territory.
ip:concept.shared-blackboardip:concept.durability-beats-coordinationip:framework.markdown-osdev:project.openclawradar:concept.agent-memoryradar:engrim-local-cli-memoryradar:memhub-shared-coding-agent-memoryradar:holaos-shared-agent-workspaceradar:agentdrive-persistent-shared-storageradar:concept.sqlite
queries asked of Scott's wikis
- agent memory architecture — per-agent stores vs shared memory substrate
- agent-maintained wiki conventions as long-term memory for coding agents
- SQLite as local-first memory or knowledge store in my dev projects
- multi-agent shared context — write conflicts, attribution, namespaces
- MCP servers and memory tools I've built or evaluated
- local-first no-cloud positions on agent infrastructure
Measured heat
now 0 pts/hpeak 1 pts/hcomments 0/hpeers p0momentum: steady2 platformsage 226h
points/hour across evidence · reading as of 2026-10-12 02:59:37.977291+11:00 · deterministic, not a model opinion
How the heat travelled
pace: p22 vs 1188 stories at the 168h mark (now 226h old) — ahead of aafp-commons-signed-agent-notebook (2.0x), behind agentgate-signed-agent-receipts (0.7x)
Evidence (2) — ⭐ canonical anchor
Interpretation history
2026-10-02T10:40:33Z
origin walked (opencode/cheap-glm, conf 0.82): anchor reddit.post.1wvmps7 -> echo.blog.f985c2c9a9 by lanbass869-cell (pseudonymous solo developer of MemTether)
2026-10-02T10:34:49Z
grounded: converges/medium — Independently arrives at Scott's shared-blackboard / durability-beats-coordination position — one durable external medium that replaceable coding agents all rea
2026-10-02T10:25:50Z
case created — A distinct released artifact with a crisp, resolvable local-shared-memory claim that no open case carries (closest neighbors — AgentDrive, HolaOS, ES Archive — are different mechanisms and different owners), earning a seed slot despite near-zero engagement.
Decision trace
- 10-02 20:40promote_anchororigin walk conf 0.82
- 10-02 20:34groundIndependently arrives at Scott's shared-blackboard / durability-beats-coordination position — one durable external medium that replaceable coding agents all read and write with attribution — but
- 10-02 20:25createA distinct released artifact with a crisp, resolvable local-shared-memory claim that no open case carries (closest neighbors — AgentDrive, HolaOS, ES Archive — are different mechanisms and different o