v1.8.0

[rahilp]

What's Changed

This release ships four merged PRs. The most important one is a bug fix. If you've noticed entries disappearing from recall after updates, this is why.

Bug Fixes

Re-embed was deleting vectors it just inserted (#136)

Contributed by @mikestanley00

Single-chunk entries could silently vanish from recall after an update. storeEntry keys a single-chunk entry by the bare entry ID, so when the update flow deleted "stale" vector IDs after re-embedding, it was deleting the new vector (same ID). Fixed by diffing old vector IDs against freshly inserted ones before deletion. Only genuinely orphaned vectors get removed now. Affected entries will resurface on next update or re-store.

New Features

Semantic compression: rolling digests (#127)

A nightly cron compresses tags with more than 10 entries into a single synthesized digest. Source entries are penalized 0.4x in recall scoring so digests surface above originals. There's also an on-demand endpoint to trigger compression from the Settings UI without waiting for cron.

REST parity for recall and forget (#131)

GET /recall and POST /forget now work as direct REST routes, mirroring the MCP tools exactly (time-decay reranking, vector cleanup on delete). GET /list also picks up tag, after, and before filter support to match list_recent. Error responses are standardized across the API.

One-command AI client setup (#134)

New setup scripts (connect-ai-clients.sh / connect-ai-clients.ps1) append global system instructions to ~/.claude/CLAUDE.md and ~/.codex/AGENTS.md, and register your worker's /mcp endpoint with both clients in one run.

Other

• Star History chart added to README (Add Star History section to README #128)

---

Full changelog: v1.7.0...v1.8.0

---

This discussion was created from the release v1.8.0.

[phillipadsmith]

@rahilp What is the recommended path to "upgrade" the second brain?

[rahilp]

Upgrading is simple: just sync your fork and redeploy. The Worker migrates its own database schema on the first request after each deploy, so you never need to touch the D1 console or run any SQL by hand.

One-click deploy users:

Go to your fork (github.com/YOUR-USERNAME/second-brain-cloudflare)
Click Sync fork → Update branch — this triggers a redeploy
That's it. The next request auto-applies any schema changes.
Terminal / manual deploy users:

git pull upstream main   # add the remote first if needed:
                         # git remote add upstream https://github.com/rahilp/second-brain-cloudflare.git
npm install
npm run deploy

No new environment variables are needed unless a specific release note says otherwise.

Full details are on the wiki: How to Upgrade