# Aletheia 0.2.0 release notes

Released 2026-11-12.

[npm 0.2.0](https://www.npmjs.com/package/aletheia-mem/v/0.2.0) · [GitHub release](https://github.com/mohamed-ashraf-elsaed/aletheia-mem/releases/tag/v0.2.0) · [Changes since 0.1.13](https://github.com/mohamed-ashraf-elsaed/aletheia-mem/compare/v0.1.13...v0.2.0)

```bash
npm install -g aletheia-mem@0.2.0
```
### Security

- Remote mode (a non-loopback bind) served `/v1/*`, the `/v1/live` socket and `/mcp` to anyone who could reach the port when `ALETHEIA_API_KEY` was not set; the login covered only `/` and `/api/*`. In remote mode `/v1` now needs a login session or the key, `/mcp` needs the key, and the server warns at startup when no key is set. Loopback installs, the default, were not affected.
- On a loopback bind with no key, `/mcp` now answers only this computer, like `/v1`. Behind a reverse proxy or tunnel it answered anyone.
- `ALETHEIA_API_KEY` now guards every `/api` and `/v1` route, not only `/v1` and `/mcp`. The dashboard asks for the key once per tab and sends it as a bearer header; the live socket uses a one-time ticket, so the key never goes in a URL. A key must be at least 32 characters in remote mode, and repeated wrong keys are throttled.
- Every prompt is redacted again, and `<private>` blocks dropped, before any model call: the Work view refresh, summaries, compress and fact extraction.
- The sync hub checks the pairing lockout before the code, so a correct guess no longer succeeds while locked out.
- Hardening: a Host header that would change the routed path is refused; malformed percent sequences return 4xx instead of 500; the CSRF token is tied to the login session; logout closes that session's live streams; the login lockout map is bounded.

### Added

- `aletheia backup run|list|status` and `aletheia restore <file>`: scheduled local snapshots of `hub.db` (off by default, every 24 h, keep 7). Restore refuses while another process holds the database.
- Git worktree sessions share their main project's memory (`project.worktrees`, default `main`). `aletheia projects` lists project keys, and `aletheia projects fold-worktrees [--write]` folds old worktree keys into their main project. Project merges move every table in one transaction.
- Search finds Chinese, Japanese and Korean words inside stored text through a bigram channel.
- Dense (vector) results on `/v1/search`, MCP `search` and the dashboard when the optional embeddings package is installed, with a keyword fallback and a note when it is not.
- Opt-in cross-encoder rerank in search (`search.rerank`), with a time budget; the rerank benchmark rows are labelled bench only.
- Graph retrieval can be turned on with `graph.enabled` (off by default; measured on synthetic data only). `aletheia entities` and `GET /v1/entities` list entities.
- Claude Code hooks capture failed tool calls (`PostToolUseFailure`) and subagent results (`SubagentStop`); subagent rows stay out of session-start context by default.
- An opt-in file-read gate for Claude Code (`readGate.enabled`, a `PreToolUse` hook) and a `file_outline` MCP tool.
- `team_brief` and `team_search` MCP tools for team members, locally and on the sync hub.
- `aletheia import claude-memory` imports Claude Code auto-memory files, read-only and redacted.
- `aletheia connect` writes MCP config for GitHub Copilot CLI, Goose and Roo Code (from their docs, not tested on a real install).
- `aletheia folder-context <dir> [--write]`, an explicit, dry-run-first command for folder context files.
- `aletheia install claude-desktop [--write]`.
- The dashboard has team write controls, an erasure screen and a project-merge screen with a preview.
- The dashboard can be switched into the ten README languages (machine-translated), with right-to-left layout for Arabic.
- `GET /api/hub/projects/merge-plan`; `docs/openapi.json` now documents every implemented route, and a test fails when one is missing.
- A LoCoMo retrieval run against claude-mem 15.17.0 (Recall@5 43.5%, MRR 0.377, Chroma on), committed with its raw output.

### Changed

- The compress queue no longer drops sessions past 200 when no worker runs; health and doctor report it.
- `aletheia install --list`, doctor and the tools tables show capture and context separately; Windsurf has capture but no context.
- `--help` and `help` exit 0 and list every command; known errors print one line; `aletheia-server --help` prints usage.
- `/healthz` answers from a cache, and doctor waits up to about 3 s and reports a slow server as slow.
- `retention` and `context.format` are in the dashboard Settings.
- The README interfaces table lists `aletheia mcp` and `npx aletheia-mem mcp` as ways to start the stdio MCP server, in all eleven languages.

### Fixed

- The remote login page's Content-Security-Policy blocked its own login request, and the login and logout cookies were sent in one header, so browsers lost the CSRF cookie. Remote login, writes and logout work in a browser again.
- In remote mode the live socket refused the dashboard's own non-loopback origin.
- `test/refresh.test.mjs` failed from 2026-11-08 because it used the wall clock against fixture dates.
- The test suite no longer rewrites tracked `site/` files.
- Two backups written in the same millisecond overwrote each other in `aletheia connect`.
- `gemini-extension.json` still said version 0.1.0. It now carries the package version, and `scripts/release.mjs --prepare` bumps `.claude-plugin/plugin.json`, `.claude-plugin/marketplace.json` and `gemini-extension.json` with the package. `--verify` fails when one of them differs.

### Removed

- The unused result cache module, the `setupStateFile` config key and the always-501 `GET /api/work-state` route.
