Skip to content

GoodMemory 0.8.0

Choose a tag to compare

View all tags
@hjqcan hjqcan released this 14 Sep 10:44
· 31 commits to main since this release
v0.8.0
416c15b

GoodMemory 0.8.0

What changed

  • Authored note memory: keep prose or Markdown as a whole page, with governed writes, supersession lineage, and an 8,192 UTF-8 byte limit.
  • Memory artifact and directory interchange: export/import durable memory, rebuild projections, and use an opt-in read-only file mirror.
  • Fresh Codex and Claude installations enable long-record admission. Existing configured installations retain their configured policy.
  • Default workspace identity uses the normalized absolute path rather than the directory basename. Same-named projects no longer share their implicit workspace scope.
  • Kimi Code's version-pinned plugin exposes ten MCP tools, including goodmemory_write_note. Per-call approval remains in force; MCP startup has a 300-second timeout budget.
  • Optional MCP inputs may be omitted or represented as null; malformed supplied values still fail validation.

Breaking changes and migration

The deprecated public usage fields are removed: FactMemory.accessCount, FactMemory.lastAccessedAt, FeedbackMemory.lastUsedAt, RecallCandidateTrace.usageScore, RecallCandidateTrace.outcomeScore, ExperienceMetrics.touchedFactCount, and ExperienceMetrics.reinforcedFeedbackCount. Use evidenceScore where an evidence-quality trace field is needed. Retrieval does not mutate usage counters or reinforce stored memories.

Back up canonical storage and test against a separate copy before upgrading. Existing scopes are not automatically moved, merged, or deleted. Moving a project, using a worktree, or changing path spelling can select a different default scope; explicit shared workspace IDs deliberately opt out of isolation.

0.7 to 0.8 migration guide

Validation and limitations

The exact tagged source passed all 17 required release checks: canonical tests (7,183 passed, 60 skipped, zero failures), coverage gates (92.45% overall), typecheck, build, public-claim checks, projection/storage scale checks, real Postgres checks (16 passed, none skipped), Phase 73 evidence closure, plugin packaging, and exact-tarball Node and Bun consumers. The same four release assets also passed read-only source, manifest, archive, and package-integrity verification.

The additional native Kimi online end-to-end acceptance was not completed: its configured model service rejected authentication with HTTP 401. This is a disclosed remaining validation gap, not a passing Kimi runtime result. Publication proceeds without making that additional check a release blocker.

The complete internal Phase 73 Level-2 run is accounted for and accepted by its evidence gate and independent review, but it did not meet its preregistered advantage criterion. Historical source stability and external authenticity remain unproven. No public coding-uplift or benchmark claim is made by this release.

Install

npm install -g goodmemory@0.8.0
goodmemory -V

Node.js 20+ and Bun 1.3.14+ are required for the Bun-backed CLI/MCP runtime. The library also exposes the documented Node consumer boundary.

For Kimi Code:

/plugins install https://github.com/hjqcan/GoodMemory/releases/download/v0.8.0/goodmemory-kimi-plugin-0.8.0.zip

The manifest, npm tarball, deterministic evidence archive, and plugin-only ZIP are the locally prepared asset set bound to commit 416c15b479e189039709468fb319bb50c0fbe50e. They are not rebuilt during publication.

Assets 6
Loading