Engineering Decision Log in · shared project memory

Engineering Decision Log in Pennsylvania

Six months after a migration, “why did we choose this?” deserves a better answer than git blame. A MemHub decision log pairs every outcome with its constraints, alternatives weighed, and the person who called it.

Decision logs turn senior intuition into organizational capital. MemHub makes entries searchable, pinnable, and retrievable by the coding agents that otherwise keep re-proposing settled questions.

Create your shared memory

Free Community tier. Self-hosted or hosted. No external embedding API required.

acme/engineering-decision-log

synchronized

context/main

memories 41

pinned 6

contributors 9

BRIEFING FOR NEW SESSION

What changed since your last pull

3 new

decision

Standardize on idempotent write endpoints

Source: architecture.md

pattern

Repository layer owns every database transaction

Source: pull request #214

bugfix

Refresh tokens rotate atomically under load

Source: auth/session.ts

Claude Code

Cursor

Windsurf

LOCAL FIT

Why Pennsylvania engineering teams choose MemHub

In Pennsylvania, software teams ship faster when their tools share one memory instead of three silos. New engineers ramp in days because precedent is searchable, not oral history.

Because writes land locally first and synchronize later, flaky connections never block the work.

Pennsylvania: 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.
Local-first writes keep sessions productive through outages and travel.
One command onboards the whole team: memhub login, then connect for Claude Code, Cursor, Windsurf, Cline, Codex CLI, or any JSON client.

Start freeFree workspace in 2 minutes Guided demo20 min with the founding team Self-host it myselfDocker + PostgreSQL on your infra

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 in Pennsylvania, without the trade-offs.

Immutable history

Versions preserve how decisions evolved; superseded entries remain discoverable.

Pinned precedents

Pin landmark decisions so retrieval always elevates them above routine chatter.

Agent-readable

The same log steers Claude Code and Codex away from re-opening solved debates.

Review-ready exports

Filter by topic, author, or date for architecture reviews and audits.

Org-scoped visibility

Leadership sees decision flow across projects without read access to the code itself.

Frictionless capture

Log from the agent session itself; no template ceremony, no separate tool to open.

The honest comparison.

No feature-matrix gymnastics — just what changes the week you adopt MemHub.

Start free Talk to the team

Status quo	With MemHub
Context lives in heads and DMs	Memory is structured, shared, and searchable
Every agent re-learns the repo	Sessions open pre-briefed with only what changed
Rules files cap out at ~2k tokens	Unbounded versioned history stays one query away

Connect the tools already in your repository.

One command injects configuration for Claude Code, Cursor, Codex CLI, Google Antigravity, Windsurf, Cline, or any JSON MCP client.

Start free Talk to the team

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 in California Engineering Decision Log in Texas Engineering Decision Log in New York State Engineering Decision Log in Florida Engineering Decision Log in Washington State Engineering Decision Log in Massachusetts Engineering Decision Log in Colorado Engineering Decision Log in Illinois Engineering Decision Log in Georgia Engineering Decision Log in Arizona Engineering Decision Log in North Carolina Engineering Decision Log in Utah

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

Stop rebuilding context.
Start building the product.

Create workspace