v1.10.9

Engram v1.10.9 — Deferred Tools & Honest Update Checks

Reduces MCP session startup cost and makes version check failures visible.

What's New

• Deferred rare tools — 4 infrequently-used MCP tools (mem_delete, mem_update, mem_suggest_topic_key, mem_capture_passive) are now deferred at session startup, reducing the initial token cost for agents that list available tools
• Honest update check failures — when the GitHub version check fails (network error, rate limit, etc.), the error is now surfaced in the TUI instead of being silently swallowed

v1.10.8

Engram v1.10.8 — FTS5 Topic Search Fix

Fixes mem_search not finding observations by topic_key, and adds a direct search fallback for edge cases where FTS5 tokenization misses results.

Bug Fix

• topic_key added to FTS5 index — searching for topic keys like architecture/auth-model now returns matches via full-text search
• Direct search fallback — if FTS5 returns zero results, a LIKE-based fallback query runs against key text fields to catch cases where FTS5 tokenization fails (e.g., slash-separated keys, special characters)

Docs

• Added "Intended Usage" mental model page to docs

v1.10.7

Engram v1.10.7 — Sync Embedded OpenCode Plugin

Syncs the embedded OpenCode plugin template (used by engram setup opencode) with the chat.message hook fix from v1.10.6.

What Changed

• Embedded plugin updated — users running engram setup opencode now get the fixed plugin that uses chat.message instead of the broken prompt event
• Existing users who already ran setup need to re-run engram setup opencode to pick up the fix

v1.10.6

Engram v1.10.6 — OpenCode Prompt Capture Fix

Fixes the OpenCode plugin's prompt capture mechanism which stopped working after an SDK change.

Bug Fix

• Replaced dead prompt event — the OpenCode plugin now uses the chat.message hook to capture user prompts, replacing the previous prompt event handler that was silently failing after an OpenCode SDK update
• User prompts are now correctly saved to Engram's user_prompts table again

v1.10.5

Engram v1.10.5 — Claude Code Eager Memory Tools

Improves the Claude Code plugin to load memory tools eagerly at session start and leverage ToolSearch for better tool discovery.

What's New

• Eager tool loading — memory tools (mem_save, mem_search, mem_context, etc.) are loaded at session start instead of waiting for first use, reducing latency on the first memory operation
• Auto-ToolSearch — the plugin now uses Claude Code's ToolSearch capability so agents can discover Engram tools naturally through conversation context

v1.10.4

Highlights

• Fix session inflation: OpenCode Task() sub-agent executions no longer register as separate Engram sessions
• Fix pre-existing bug in session.created event handler reading the wrong property path

What Changed

• The OpenCode plugin now detects sub-agent sessions via parentID (set by OpenCode on all Task() sessions) and skips session registration for them
• Secondary detection via title suffix subagent) provides defense-in-depth
• Sub-agent session IDs are tracked to prevent cross-hook inflation via tool.execute.after
• Fixed event.properties.id to event.properties.info.id (correct path per OpenCode SDK types)

Impact

Before this fix, a single user conversation using sub-agents could generate 170+ sessions in the Engram DB. After this fix, only the real user session is registered.

Included Work

• fix(plugin): skip sub-agent session registration in OpenCode plugin

v1.10.3

Highlights

• Fix MCP process resolution on Windows and headless Linux so agent subprocesses never need PATH inheritance
• Bake a safe absolute binary fallback into the installed OpenCode plugin for headless and systemd environments
• Update Cursor docs to reflect the current .cursor/rules/ MDC format and deprecate legacy .cursorrules

Setup Improvements

• engram setup claude-code now writes a durable user-level MCP config at ~/.claude/mcp/engram.json with the absolute binary path
• engram setup opencode now writes the resolved binary path in the MCP config and bakes a 3-tier fallback (ENGRAM_BIN env, Bun.which, absolute path) into the installed plugin
• engram setup gemini-cli and engram setup codex now use the absolute binary path on all platforms, not just Windows

Docs

• Cursor section updated to recommend .cursor/rules/engram.mdc with alwaysApply: true frontmatter
• Added deprecation note for .cursorrules and version caveat for Cursor 0.43+

Included Work

• fix(setup): use absolute MCP paths on Windows
• fix(setup): resolve OpenCode MCP path in generated config
• fix(setup): bake OpenCode plugin binary fallback
• docs(cursor): clarify mdc rules path, frontmatter, and deprecation notice

v1.10.2

Highlights

• Fix Claude Code marketplace installation by correcting the plugin source schema
• Fix TUI observation detail wrapping so long content is fully readable
• Fix Claude Code /clear session-start hook matching
• Harden repo governance with stale automation, label taxonomy, security policy, code owners, and clearer contributor guidance
• Document the Windows antivirus false-positive workaround and recommend go install / source builds for technical users

Included Work

• fix: use relative path string for plugin source in marketplace.json
• fix(tui): implement dynamic text-wrapping in observation detail view
• fix(hooks): add clear to SessionStart matcher
• chore(repo): harden governance and backlog workflow

v1.10.1

What's Changed

Fix: Claude Code marketplace plugin installation (#86)

Fixed a schema validation error in .claude-plugin/marketplace.json that prevented claude plugin install engram from working.

The bug: The source object used "type": "git-subdir" instead of the correct "source": "git-subdir" key expected by Claude Code's marketplace schema.

Error users saw:

Failed to parse marketplace file: Invalid schema: plugins.0.source: Invalid input

This affected all users trying to install Engram via claude plugin marketplace add since v1.10.0.

Thanks to @Jungas80 for the fix!

Full Changelog: v1.10.0...v1.10.1

v1.10.0

What's Changed

Auto-detect project name from git remote (#70)

Project names are now resolved from git remote get-url origin instead of basename(cwd). This fixes project name mismatches in monorepos, custom folder names, and worktree setups.

Detection priority:

1. Git remote origin → extract repo name (SSH + HTTPS)
2. Git root directory name (worktree-safe)
3. CWD basename (fallback, previous behavior)

Automatic migration: On first session start, if the new name differs from the old basename, existing memories are migrated in a single atomic transaction. Idempotent — safe to run multiple times.

Affected components:

• Claude Code hooks (session-start.sh, subagent-stop.sh, post-compaction.sh)
• OpenCode plugin (engram.ts)
• New POST /projects/migrate HTTP endpoint
• Shared _helpers.sh with detect_project() function

Full Changelog: v1.9.9...v1.10.0