Releases: Gentleman-Programming/engram
v1.4.0
v1.3.1
v1.3.0
v1.2.1
Engram v1.2.1 — 100% Coverage & Contributor Standards
Reaches 100% test coverage across the entire codebase and establishes formal standards for AI-assisted contribution.
What Changed
- 100% Test Coverage: Every package (
cmd,store,server,tui,setup) is now fully covered by automated tests. - Contributor Skills: Added a
skills/directory with formal AI skills for TDD, SDD, PR workflow, and commit hygiene. - Workflow Standards: Added
CONTRIBUTING.mdestablishing an issue-first workflow and PR guardrails. - Docs Alignment: Updated README and setup scripts to reflect the new skills architecture and cross-agent support.
Full Changelog: v1.2.0...v1.2.1
v1.2.0
Engram v1.2.0 — Passive Capture & Stability
Introduces Passive Memory Capture to catch learnings automatically when agents forget to save them, alongside critical stability fixes.
What Changed
- Passive Capture: Engram now automatically extracts structured knowledge from agent outputs containing
## Key Learnings:sections. - Agent Adapters: Added support for passive capture in Claude Code, OpenCode, Gemini, and Codex integrations.
- Bug Fix: Resolved a crash in export/sync caused by
NULLvalues in theuser_promptstable. - Hardening: Added comprehensive regression tests for data sorting and NULL handling.
Full Changelog: v1.1.0...v1.2.0
v1.1.0
Engram v1.1.0 — TUI Dashboard & Recency Sorting
Improves the TUI dashboard layout and ensures your most active projects and sessions always appear at the top.
What Changed
- Vertical Project List: The dashboard now displays a clean vertical list of your top 5 active projects instead of a hard-to-read single line.
- Recency Sorting: Projects and Sessions are now sorted by most recent activity (latest observation saved), so your current context is always instant.
Full Changelog: v1.0.2...v1.1.0
v1.0.2
Engram v1.0.2 — Migration Fix
Fixes a critical migration issue where legacy observations could end up with invalid IDs during the upgrade process.
What Changed
- Fix: Rebuilt the legacy migration logic to ensure valid, unique IDs are generated when porting old data to the new schema.
Full Changelog: v1.0.1...v1.0.2
v1.0.1
Engram v1.0.1 — Homebrew Formula Migration
Switches Homebrew distribution from Cask to Formula, so brew upgrade engram works properly.
What Changed
- Switched
.goreleaser.yamlfromhomebrew_caskstobrews(Formula) - Added migration instructions in README for users coming from the Cask
Upgrade
If you had the Cask (v1.0.0 or earlier):
brew uninstall --cask engram 2>/dev/null
brew install gentleman-programming/tap/engramFrom now on, upgrades work normally:
brew upgrade engramFull Changelog: v1.0.0...v1.0.1
v1.0.0
Engram v1.0.0 — Full Agent Parity
Engram now supports four AI coding agents with first-class setup, MCP registration, and compaction recovery out of the box.
What's New
Gemini CLI & Codex Setup Support
One command to get full memory integration — no manual config editing:
engram setup gemini-cli # MCP + system prompt + compaction recovery
engram setup codex # MCP + instruction files + compact promptCompaction Recovery for All Agents
Every supported agent now has automatic compaction recovery — when context gets summarized, Engram ensures the agent persists the summary and recovers previous session state:
| Agent | Compaction Strategy |
|---|---|
| OpenCode | System prompt injection + compaction hook |
| Claude Code | Native hooks (post-compaction.sh) + Memory Protocol skill |
| Gemini CLI | ~/.gemini/system.md + GEMINI_SYSTEM_MD=1 env override |
| Codex | model_instructions_file + experimental_compact_prompt_file in config.toml |
Supported Agents
| Agent | Setup Command | MCP | Memory Protocol | Compaction Recovery |
|---|---|---|---|---|
| OpenCode | engram setup opencode |
✅ | ✅ | ✅ |
| Claude Code | engram setup claude-code |
✅ | ✅ | ✅ |
| Gemini CLI | engram setup gemini-cli |
✅ | ✅ | ✅ |
| Codex | engram setup codex |
✅ | ✅ | ✅ |
Upgrade
brew upgrade engramOr grab the binary from Releases.
Full Changelog: v0.1.9...v1.0.0
v0.1.9
Hotfix — Migration fix for upgrading users
Bug Fixes
-
Indexes created before columns existed. The
CREATE INDEXstatements for new columns (scope,topic_key,normalized_hash,updated_at,deleted_at) ran in the initial schema batch before theALTER TABLE ADD COLUMNcalls. This causedSQL logic error: no such column: scopefor users upgrading from pre-0.1.8 databases. Fixed by removing the duplicate index definitions from the initial batch — they already existed in the correct location after the column migrations. -
Non-constant default in ALTER TABLE. The
updated_atcolumn migration usedDEFAULT (datetime('now')), which SQLite does not allow inALTER TABLE ADD COLUMN(only inCREATE TABLE). Changed to a constant empty-string default; the existing backfillUPDATEalready setsupdated_at = created_atfor migrated rows.
Root Cause
Both bugs only affected users upgrading from pre-0.1.8 databases. New installations were unaffected because CREATE TABLE handles the full schema including expressions and indexes in one pass.
Notes
- No data changes, no new features.
- Safe to upgrade from any previous version.
- Full test suite passing.