Skip to content

v2.0.0-rc.1

Pre-release
Pre-release

Choose a tag to compare

View all tags
@github-actions github-actions released this 29 Aug 03:53
v2.0.0-rc.1
2732d68
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Engram v2.0.0-rc.1

Prerelease: This release candidate is for testing and feedback. Do not replace stable production installations with it. Keep a stable v1.20.0 installation available.

This RC contains a broad reliability and compatibility pass across the local store, sync paths, agent integrations, and release tooling.

Highlights

Binary self-testing

Released binaries now include isolated local checks (#868, #867):

  • Reliability checks for database initialization, migration, save, search, context, and concurrent writes.
  • Performance measurements for local search.
  • Stable JSON reports for automation and issue reports.
  • Temporary storage only; configured user data is not touched.

Project and memory safety

  • Safer project ownership, normalization, consolidation, and legacy-session recovery (#801, #813, #846).
  • New engram projects rescue-ownership recovery flow.
  • Invalid observation titles/content are rejected before persistence or sync queue side effects (#802).
  • HTTP searches with no results now return [], not null (#862).

Agent integrations

  • More authoritative and fail-closed Pi/OpenCode session attribution (#730, #734).
  • Improved Pi startup, retry, cleanup, and duplicate-spawn behavior (#817, #827).
  • Native Windows Codex stop/session handling (#724, #729).

Sync and Cloud reliability

  • Large initial Cloud replays are split into deterministic 4 MiB chunks with resumable acknowledgements (#834).
  • Irreparable mutations are quarantined without fabricating acknowledgements (#811).
  • Better diagnostics for unenrolled or undeliverable mutations (#819).
  • Prompt and relation deletion/replay evidence is preserved more reliably (#844, #845).

Compatibility and risk areas

No merged PR in the reviewed range carries the type:breaking-change label, and no explicit breaking commit was verified. Testers should still pay particular attention to:

  • Legacy databases with NULL/blank session ownership. Run engram doctor; use engram projects rescue-ownership ... when instructed.
  • Project consolidation: only normalization-equivalent names are safely merged; fuzzy matches are no longer treated as automatic ownership.
  • Pi/OpenCode integrations: confirmed runtime session identity is authoritative; model-supplied identities may be ignored or rejected.
  • Cloud autosync compatibility: older Cloud servers without mutation endpoints may report server_unsupported or transport_failed.
  • Cloud and Postgres behavior requires separate testing; it is not covered by the local binary self-test.

RC validation

Run these commands with the RC binary:

engram test
engram test --quick
engram test --quick --json > engram-self-test.json

engram test runs both suites. --quick uses a bounded workload. JSON reports use schema engram-self-test/v1.

Please attach the following to RC feedback:

  • engram version
  • OS and architecture
  • Exact command and exit code
  • Human-readable output or engram-self-test.json
  • stderr and the failed scenario/error, if applicable
  • Separate Cloud/Postgres logs and reproduction steps for remote issues

The self-test is offline, uses a temporary directory, and does not read ENGRAM_DATA_DIR, user databases, Cloud credentials, configured endpoints, or agent plugins.

Distribution

Homebrew stable remains on v1.20.0. Download RC binaries from this GitHub prerelease, not Homebrew.

Supported binaries:

  • macOS: darwin_amd64, darwin_arm64
  • Linux: linux_amd64, linux_arm64
  • Windows: windows_amd64, windows_arm64

Full comparison: v1.20.0...v2.0.0-rc.1

Assets 9
Loading