Skip to content

Releases

v0.24.0

Choose a tag to compare

@github-actions github-actions released this 14 Nov 17:05
f4be2c4

Engram v0.24.0

Release candidate prepared for the v0.24.0 GitHub Release (v0.21.2 remains the latest published release until the signed v0.24.0 tag is pushed; registry publication to crates.io, PyPI, and npm is a separate decision).

Security

  • palace_visualize saving is a filesystem write — a call with output_path now requires scoped_write within ENGRAM_EXPORT_BASE_DIR, otherwise maintenance, like memory_export_markdown, and permission_mode_status exposes output_path in write_flag_params. Paths outside the export base are refused before any directory is created, .. components are rejected unconditionally, active SQLite artifacts are refused both before directory creation and after parent canonicalization across CLI and MCP callers, symlinks and multi-link files (nlink > 1) are rejected, and outputs are published via an owner-only (0600) sibling temp file and atomic rename.
  • GET /v1/events is workspace-scoped for restricted principals — a keyless (anonymous loopback) stream opened without workspace now receives default events only instead of every workspace's events and content previews.
  • Context assembly and graph expansion stay in scope — memory_build_context, memory_get_injection_prompt, and memory_prepare_context normalize and authorize workspace, workspaces, and filters.workspace consistently with central MCP permission checks, keep restricted principals within their allowed workspace, advance depth 2–3 graph frontiers only through authorized in-scope memories, and filter include_graph crossrefs so foreign-workspace edges are never exposed.
  • Keyless HTTP and CORS align on Host and Origin — without an API key, /mcp, /v1/mcp and /v1/events answer 403 to requests whose Host or Origin does not name this machine (DNS rebinding, cross-site requests). ENGRAM_HTTP_ALLOWED_HOSTS extends the Host allowlist; blank ENGRAM_CORS_ORIGINS normalizes to unset, empty comma tokens and empty Origin headers are rejected, and both CorsLayer preflight (OPTIONS) and keyless checks accept case-insensitive loopback Origin URIs (localhost, 127.0.0.1, [::1], any port) by default; see MCP_AUTH.
  • Multimodal path confinement and handler scope guards (A-5, A-6, A-7, Q-A) — memory_search_by_image requires ENGRAM_MEDIA_BASE_DIR in read_only/scoped_write modes (escalating to maintenance when unset or blank), all media path validators refuse active SQLite artifacts before canonicalization, memory_digest authorizes inner context_build_bundle calls, harness_status restricts include_git to unrestricted writers, and memory_agent_status scopes total_memories to the target workspace.
  • Bundled SQLite 3.54.1 (RUSTSEC-2026-0459, CVE-2026-119375) — rusqlite 0.31 → 0.41.1 and libsqlite3-sys 0.28.0 → 0.39.1 in the root and fuzz/ lockfiles. The previous bundled SQLite 3.45.0 could return uninitialized page-cache memory for a database opened with a -wal of a different page size. No schema, MCP or SDK change; rusqlite keeps the same feature surface (cache and fallible_uint are now explicit opt-ins).
  • Markdown filesystem import (RISK-0011) — scoped writers require an administrator-configured root; unconfined reads require maintenance even during review. Bounded directory-relative reads reject links, special files and SQLite artifacts before opening regular files. Existing IDs are authorized by their stored workspace, cross-workspace ID overwrites against an explicit target workspace are rejected, and confirmed batches authorize/classify/apply within one transaction. Pre-commit failures roll back; completion uncertainty is explicit. See compatibility notes.
  • Markdown filesystem export — memory_export_markdown is a write operation: scoped writers need an administrator-configured ENGRAM_EXPORT_BASE_DIR; unconfined destinations require maintenance privileges. Linux/macOS directory-relative writes reject unsafe components, symlinks, hard links, active SQLite artifacts and directory ACLs, and publish private temporary files by atomic rename. Other platforms fail closed. See compatibility notes.
  • Batch tools enforce per-item workspaces — memory_create_batch and memory_ingest_fact_batch authorize every item's workspace (central check, gRPC pre-check and handlers), closing a cross-workspace write introduced by the search/auth hardening commit e04d3307. Batch item arrays are derived from the catalog schema and fail closed on unreadable nested workspace claims.
  • Resource subscriptions are principal-aware — resources/subscribe and resources/unsubscribe apply the same workspace policy as resources/read.
  • memory_search_suggest is workspace-scoped — restricted principals get spelling corrections built only from their own workspace vocabulary.
  • permission_denial_for_mode fails closed for unknown tools.
  • One tools/call unwrap point — HTTP and gRPC unwrap the envelope once and authorize the same bare arguments the dispatcher sees; name/arguments keys inside real tool arguments are no longer treated as an envelope. A caller's per-call _permission_mode self-restriction is still applied by the dispatcher, so its denial stays in the tool result (HTTP 200).
  • Log redaction (RISK-0002) — sync/cloud, hooks, multimodal, engram-server HTTP/WebSocket transport startup errors, and the watcher (including its daemon) no longer log bucket/object keys, workspace and tool names, filesystem paths, engram_url, dry-run memory content, subprocess stderr or raw error text; errors are logged by class (ENGRAM_LOG_ERROR_DETAIL=1 restores detail for debugging).
  • Cryptographic release-tag verification (R3) — Added scripts/verify-release-tag.sh and docs/releases/allowed-signers, wired into .github/workflows/sdk-release.yml across preflight, publish-python, and publish-npm with anti-self-authorization and anti-ref-shadowing (materializing both verifier script and trust store from canonical refs/remotes/origin/main via --end-of-options), and hardened scripts/sign-candidate-manifest.sh option/PEM/leading-dash guards.
  • Lifecycle, policy, compression, and server hook authorization (Unit 1, Unit 3) — Added 12 lifecycle/policy/compression by-ID tools (memory_set_lifecycle, memory_lifecycle_update, memory_score, memory_promote, memory_explain, memory_reconcile_conflict, memory_promote_to_permanent, memory_boost, memory_set_expiration, memory_compress, memory_decompress, memory_compress_for_context) to ID_SCOPED_TOOLS with in-transaction ensure_memory_access checks and single-ID decay scoping; engram-server lifecycle hooks now enforce _permission_mode / ENGRAM_PERMISSION_MODE, require Permission::Write on ResourceType::Memory, reject unauthorized fallback to "default", and skip PostToolUse reinforcement on error responses.
  • Dependency advisories — zip 9.0.5 and duckdb 1.10506.1 (RUSTSEC-2026-0367/0368/0369), tokio 1.53.3 (RUSTSEC-2026-0386), rustls-webpki 0.103.16, webpki-roots 1.0.11 and ctutils 0.4.6 (RUSTSEC-2026-0382/0381/0385), rustix 1.1.6 (RUSTSEC-2026-0486), quinn-proto 0.11.19 (RUSTSEC-2026-0523/0524), and quinn-udp 0.5.16 (RUSTSEC-2026-0538); crypto-bigint 0.5 removed from the graph (RUSTSEC-2026-0387) by not enabling aws-sdk-s3/sigv4a.

Added

  • RFC 0009, 0010, and 0011 Implemented — Promoted and wired MCP Contract Validation (docs/rfcs/0009-mcp-contract-validation.md), Permission Modes (docs/rfcs/0010-permission-modes.md), and Deterministic Model Routing (docs/rfcs/0011-model-routing.md, governance/models.toml, scripts/select-model.py).
  • MCP Error Normalizer (G-6, G-7, G-10) — Added src/mcp/error_normalizer.rs and upgraded context/blocks.rs, compression.rs, dream.rs, memory_crud/read_update_delete.rs, and search.rs so wrong-typed id/limit/offset parameters and domain errors emit RFC 0006 structured ToolError payloads (invalid_params, memory_not_found, validation_error).
  • Zero-Drift Python & TypeScript SDKs (v0.7.0, G-2, G-4, G-5) — Aligned all Python and TypeScript SDK resource methods with the MCP server tool registry, routed resources/* calls over JSON-RPC (_rpc_call / rpcCall), ratcheted docs/quality/sdk-contract-drift-baseline.json from 161 entries down to 0 (known_drift: []), and added TypeScript isError: true structured EngramError(message, code, details) plus timeout/connection_error parity.
  • Server Lifecycle Hooks & Cloud Sync Worker (#237, C6) — Wired SessionStartHandler, PostToolUseHandler, and SyncWorker::start_background into engram-server startup and shutdown lifecycle.

Changed

  • Search (from e04d3307): catalog default limit is 20, offset and include_archived are accepted, SearchOptions.offset is public, and memory_search_by_identity / memory_session_search are read-only. Python and TypeScript SDKs default search to limit 20 and accept offset (Python also include_archived).
  • HNSW is opt-in — hnsw_enabled defaults to false until the benchmark required by RFC 0003 exists; enable it with ENGRAM_HNSW_ENABLED / --hnsw-enabled. When off, no index is built at startup or maintained on writes. HNSW widening stops after two empty hydration rounds.
  • Snapshot loader reads archive entry names from the central directory and rejects undecodable names.
  • DuckDB bundled engine 1.4.4 → 1.5.6; sqlite-vec is a dev-dependency (benchmarks only).
  • CI pins cargo-audit 0.22.0 and cargo-outdated 0.19.0 (--locked); the TypeScript live lane uses Node 24; the docs job runs the public-claims, advertised-contracts and release-version checks.
  • bump-version.py verifies lockfiles and __version__ and adds ...
Read more

v0.21.2

Choose a tag to compare

@github-actions github-actions released this 16 Jun 01:39
a11337a

Engram v0.21.2

Release date: 2026-06-16

Changed

  • Release notes source — GitHub Release bodies now come from the reviewed
    CHANGELOG.md section for the requested tag instead of GitHub-generated
    notes, preventing reruns from expanding old PR lists.
  • Release automation hygiene — Release preflight now blocks existing tags
    unless overwrite_assets=true is explicitly requested, and Homebrew formula
    updates skip no-op commits while checking for the tap token up front.
  • Public claims hygiene — README, roadmap, and release docs now use more
    conservative wording and document which public-use claims still need
    publication-time fact-checking.

Full changelog: v0.21.1...v0.21.2

v0.21.1

Choose a tag to compare

@github-actions github-actions released this 15 Jun 18:22
60c36b8

Engram 0.21.1

This patch release focuses on release readiness, public documentation hygiene, and the first extracted product strategy notes from the old competitive-research branch.

Highlights

  • Adds conservative public strategy documentation under docs/strategy/ and links it from the docs index and roadmap.
  • Refreshes README, roadmap, AI guide, and changelog wording to avoid stale transport, version, performance, and competitor-positioning claims.
  • Keeps required GitHub PR checks reportable for documentation-focused changes.
  • Updates release automation so Homebrew tap updates run when HOMEBREW_TAP_TOKEN is configured and skip cleanly when it is not.
  • Updates release workflow actions for the GitHub Actions Node 20 to Node 24 migration.

Verification

  • git diff --check
  • bash docs/harness/bin/doctor.sh
  • cargo publish -p engram-core --dry-run --allow-dirty
  • make ci
  • GitHub required checks passed on PRs #81, #82, #83, and #84.
  • Manual Release workflow with HOMEBREW_TAP_TOKEN passed and pushed the Homebrew formula.

Distribution

  • Crate: engram-core = 0.21.1
  • GitHub release assets: macOS and Linux tarballs for x86_64 and aarch64
  • Homebrew tap: aiconnai/homebrew-engram updated to the published asset checksums

Public marketing, competitive, performance, and benchmark claims should still be fact-checked before reuse outside the repository docs.

Full changelog: v0.21.0...v0.21.1

v0.21.0

Choose a tag to compare

@github-actions github-actions released this 11 May 01:11

Full Changelog: v0.20.0...v0.21.0

v0.20.0

Choose a tag to compare

@github-actions github-actions released this 11 May 00:15

Full Changelog: v0.15.0...v0.20.0

v0.15.0

Choose a tag to compare

@github-actions github-actions released this 10 Mar 11:49

Full Changelog: v0.11.0...v0.15.0

v0.11.0 — Cognitive Memory Engine

Choose a tag to compare

@limaronaldo limaronaldo released this 09 Mar 18:20

Engram v0.11.0 — Cognitive Memory Engine

All 19 phases complete. 672+ tests, schema v30, 207+ MCP tools.

New Phases (E–K)

  • Phase E: Memory Compression & Consolidation — 30x semantic compression, online synthesis, sleep-time consolidation
  • Phase F: Agentic Memory Evolution — Historical memory update, retrieval utility scoring (MemRL Q-values), emotional & reflective memory
  • Phase G: Advanced Graph Intelligence — Conflict detection/resolution, Hebbian coactivation, semantic triplet matching (SPARQL-like)
  • Phase H: Autonomous Memory Agent — Proactive acquisition, 4-pass gardening pipeline, observe→decide→act agent loop, engram-agent binary
  • Phase I: Retrieval Excellence — Multi-provider embeddings (Ollama, Cohere, Voyage, ONNX), MMR diversity, semantic cache, neural reranking, explainability, feedback loop
  • Phase J: Context Engineering — Fact extraction, prompt construction (3 strategies), self-editing memory blocks (Letta-inspired)
  • Phase K: Temporal Graph & Platform Maturity — Temporal knowledge graph with validity periods, 5-level hierarchical scoping, LOCOMO/LongMemEval/MemBench benchmark suite

Highlights

  • 207+ MCP tools (46 new across 7 feature flags)
  • Schema v30 (15 new tables, 11 new columns)
  • 672+ tests passing
  • New binary: engram-agent for autonomous memory management
  • New binary: engram-bench for standardized benchmarks
  • SDKs updated to v0.2.0 (Python + TypeScript) with all new methods

Feature Flags

Flag Phase Description
compression E Semantic compression & consolidation
agentic-evolution F Utility scoring, sentiment, reflection
advanced-graph G Conflicts, coactivation, triplets
autonomous-agent H Agent loop, gardening, proactive scan
retrieval-excellence I Multi-provider embeddings, MMR, neural rerank
context-engineering J Facts, prompt builder, memory blocks
temporal-graph K Temporal edges, scoping, benchmarks

Install

cargo install engram-core

Or with all features:

cargo install engram-core --features full

Links

Full Changelog: v0.6.0...v0.11.0

v0.6.0

Choose a tag to compare

@github-actions github-actions released this 09 Mar 02:17

Full Changelog: v0.5.0...v0.6.0

v0.5.0

Choose a tag to compare

@github-actions github-actions released this 13 Feb 22:24

Full Changelog: v0.4.1...v0.5.0

v0.4.1

Choose a tag to compare

@github-actions github-actions released this 13 Feb 22:03

Full Changelog: v0.4.0...v0.4.1