v0.2.0 — Migrate to v1 Cloud API

What's Changed

Hard-cut migration from the deprecated v0 EverMind Cloud API to v1. The v0 API is slated for removal — all endpoints have been upgraded.

Endpoint changes

Operation	v0 (removed)	v1
Add memory	POST /api/v0/memories	POST /api/v1/memories/group / POST /api/v1/memories
Search	GET /api/v0/memories/search (curl hack)	POST /api/v1/memories/search
List	GET /api/v0/memories	POST /api/v1/memories/get

Highlights

• No more curl hacks — v0 required GET with a JSON body (unsupported by fetch). v1 uses POST everywhere, so the proxy and API client now use native fetch.
• Dashboard iterates groups — v1 filters require a real group_id or user_id. The dashboard now fetches the local groups list and paginates per group.
• Response shape migration — search results read from data.episodes[].summary; get results read from data.episodes[].episode. All downstream callers (hooks, MCP server, slash commands) required no changes — the public API client contracts are preserved.
• Dead code cleanup — removed unused generateMessageId, debugLog, execSync imports.

Upgrade

Existing users:

claude plugin marketplace add https://github.com/EverMind-AI/evermem-claude-code
claude plugin install evermem@evermem --scope user

Or re-run the install script:

curl -fsSL https://raw.githubusercontent.com/EverMind-AI/evermem-claude-code/main/install.sh | bash

Full Changelog

v0.1.2...v0.2.0

v0.1.2: Migrate API endpoints from v1 to v0, heatmap fixes

- Update all API endpoints from /api/v1/ to /api/v0/
- Apply yellow brand color to heatmap grid cells and legend
- Use dynamic quartile thresholds for heatmap levels

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>