01
decision
Standardize on idempotent write endpoints
Source: architecture.md
Engineering Decision Log across · shared project memory — local-first · offline-ready
Engineering Decision Log across Canada
Enforce the habit without ceremony. Pair with a PR hook, filter by topic/author/date for audits — decisions that stay found, not filed and forgotten.
Stop re-litigating the same architecture debate. MemHub is an engineering decision log that sticks — logged mid-task in the terminal, with author and timestamp auto-attached.
Start free — get briefed in 2 min
Free for 1 project · No card · Self-host or we host · No external API
acme/engineering-decision-log
synchronizedcontext/main
memories 41
pinned 6
contributors 9
BRIEFING FOR NEW SESSION
What changed since your last pull
02
pattern
Repository layer owns every database transaction
Source: pull request #214
03
bugfix
Refresh tokens rotate atomically under load
Source: auth/session.ts
Claude Code
Cursor
Windsurf
WHY IT MATTERS HERE
Why Canada engineering teams choose MemHub
Across Canada, software teams ship faster when their tools share one memory instead of three silos. Mixed toolchains stop fragmenting knowledge across vendor-specific stores.
Teams operating under PIPEDA can point at a concrete architecture instead of promises.
- Canada: connect Claude Code, Cursor, Windsurf, Cline, Codex CLI, or Antigravity to one shared memory. It also plugs into any CLI that speaks MCP or reads a JSON config.
- Data residency you control — run MemHub on infrastructure inside Canada or let us host it.
- One command onboards the whole team: memhub login, then connect for Claude Code, Cursor, Windsurf, Cline, Codex CLI, or any JSON client.
UNIVERSAL COMPATIBILITY
Plugs into any CLI or development tool you use.
If it speaks MCP or reads a JSON config, MemHub plugs in. One command wires the majors; everything else joins as a generic client.
- Claude Code
- Cursor
- Windsurf
- Cline
- Codex CLI (GPT)
- GitHub Copilot
- Google Antigravity
- Gemini CLI
- Aider
- OpenCode
- CI bots via REST
WHAT YOU GET
Engineering Decision Log across Canada, without the trade-offs.
01
See across repos
Leadership views decision flow org-wide without read access to the code itself.
02
Log where you decide
Mid-task, in the terminal — no template ceremony, no separate tool. Friction near zero, habit sticks.
03
History you can trust
Immutable versions — see how a call evolved, with superseded entries still discoverable.
04
Pin the precedents
Landmark decisions pinned to top — reviews surface them before debate restarts.
05
Agents stop re-litigating
Same log steers Claude Code/Codex away from solved questions — fewer regressions.
06
Reviews in one query
Filter by topic/author/date — export the narrative for architecture reviews and audits.
The honest comparison.
No feature-matrix gymnastics — just what changes the week you adopt MemHub.
| Without MemHub | With MemHub |
|---|---|
| Context lives in heads and DMs → onboarding takes days | Structured, searchable memory → new dev/agent productive in minutes |
| Every agent re-learns the repo from scratch | Sessions open pre-briefed with only what changed — zero re-explaining |
| Rules files cap out at ~2k tokens | Unbounded versioned history stays one query away — never cap again |
| Decisions re-litigated, bugs re-introduced | Pinned invariants prevent regressions — agents respect past calls |
Keep your stack. Add shared memory.
One command for Claude Code, Cursor, Codex, Windsurf, Cline or any MCP client. No new editor. Setup in 2 minutes, works offline.
repository terminal
$ npm install --global @simplexlat/memhub
$ memhub login
✓ project resolved · context ready · memory synchronized
Questions, answered straight.
Can we enforce that certain decisions get logged?
Teams typically pair MemHub with a PR checklist or hook that prompts a decision entry whenever specific paths change.
How is this different from ADRs in git?
ADRs document decisions made in meetings; MemHub also captures the hundreds of micro-decisions agents and engineers make daily, with the same rigor and none of the ceremony.
What happens when our connection drops?
Nothing interrupts the work. Writes commit to the local SQLite outbox and synchronize automatically when the shared service is reachable again.
Can we try it without sending data anywhere?
Yes — the local engine works fully offline, and the self-hosted stack keeps even the shared layer on your own PostgreSQL.
How much does it cost?
A Community tier is free, and the Team plan adds multi-project contexts, seats, and higher synchronization limits. Self-hosting is unlimited.
MORE LOCATIONS
Engineering Decision Log across the United StatesEngineering Decision Log across the United KingdomEngineering Decision Log across IrelandEngineering Decision Log across GermanyEngineering Decision Log across FranceEngineering Decision Log across SpainEngineering Decision Log across PortugalEngineering Decision Log across ItalyEngineering Decision Log across the NetherlandsEngineering Decision Log across BelgiumEngineering Decision Log across SwitzerlandEngineering Decision Log across Austria
EXPLORE OTHER USE CASES
AI Agent Memory
Give every AI coding agent a persistent, team-wide memory.
MCP Memory Server
A hosted MCP memory server your whole team connects to in one command.
Claude Code Memory
Claude Code memory that survives sessions and reaches the whole team.
Cursor Memory
Carry Cursor context across sessions, machines, and teammates.
Codex CLI Memory
Persistent context for Codex CLI — personal today, shared tomorrow.
Cross-Agent Memory
One memory behind Claude Code, Cursor, Codex CLI, and Antigravity.
Developer Knowledge Base
A living knowledge base that writes itself while your team codes.
Self-Hosted AI Memory
Run the entire memory stack on your own PostgreSQL — nothing leaves.
Coding Agent Context
Context engineering for coding agents — brief, don’t dump.
Agent Memory Database
A real database behind agent memory — PostgreSQL, pgvector, row-level security.
Windsurf Memory
Persistent Windsurf context shared with every other agent on the team.
Cline Memory
Give Cline a memory that survives tasks, machines, and teammates.
Copilot Team Memory
What Copilot’s custom instructions can’t hold, MemHub remembers.
Antigravity & Gemini Memory
Persistent context for Google Antigravity, Gemini CLI, and the agents around them.
THE NEXT SESSION STARTS HERE — 2 MIN SETUP