v0.5.1 — redaction rules for a team or a user; the Panel in seven languages

Note

v0.5.1 replaces v0.5.0, whose release was withdrawn the same day. It has every change of v0.5.0, plus a memory-core image that builds where outbound HTTP is blocked. If you already run v0.5.0 (built from main, or the 0.5.0 images), there is nothing to migrate.

Before you upgrade

Redaction rules gain a team and a user level, and the Panel gets its own Redaction page and seven languages. Check these before you upgrade; each one links to its section in UPGRADE → To 0.5.1 and To 0.5.0.

If …	Then …
redaction.patterns (AGENT_MEMORY_REDACTION_PATTERNS) holds patterns that should stay with administrators	Every member can now read them, with the rules for all teams (who reads the rules)
A script calls /v3/meta/redaction-rule/*	Nothing to change: without team_id or user_id it works on the rules for all teams, as before; list answers with two more fields (rules for a team or a user)
People open Redaction under Metadata in the Panel	It has its own entry in the menu now

Warning

Going back to 0.4.3 after this upgrade means restoring the backup. memory-core runs schema migration 7 at startup. Nothing is converted, but 0.4.3 refuses data at schema version 7: it would apply a team's or a user's redaction rules to every team, and drop their level when it saved one. upgrade.sh takes the backup; UPGRADE → Roll back restores it.

git fetch --tags && git checkout v0.5.1
./upgrade.sh

amem and the client plugins have not changed apart from their version number, so updating clients is optional (REMOTE-CLIENTS §4).

What's new

• Redaction rules for a team or a user (#79). On top of the rules for all teams, a team's admins add rules for their team, which apply to its members' writes and its shared scenes and persona; each user adds their own, which apply to their writes in every team. A level only adds redaction; none can turn off a level above it. Members read the rules for all teams and their teams'; a user's rules are seen by that user and system admins. Each level has its own limit of 50 enabled rules. Only the kinds of the rules for all teams are unique, so a marker such as [REDACTED:phone] may come from any level (DISTILLATION §7).
• Redaction has its own page in the Panel (#79), with tabs for all teams, a team and a user. Rules a viewer cannot change are shown read-only, with the levels above listed under them. Try it at a user's level can add one of their teams, as their writes there get.
• The Panel speaks seven languages (#78): English, 繁體中文, 简体中文, Français, Tiếng Việt, Español and Deutsch. It starts in the browser's language (zh-CN, zh-SG and zh-Hans are Simplified Chinese; any other Chinese tag, plain zh included, is Traditional Chinese) and keeps the one picked from the menu in the sidebar or on the sign-in page. Numbers and relative times follow the language (Panel README).
• AGENT_MEMORY_DISTILLATION_LLM_TIMEOUT_MS sets llm.timeoutMs, the timeout of each call to the distillation LLM (default 180000), without editing the config file (#75).

Fixed

• The memory-core image builds where outbound HTTP is blocked: its runtime stage fetches Debian packages over HTTPS instead of from http://deb.debian.org, so install.sh and upgrade.sh work on such networks (#81).
• The worker's last_error (pipeline status, Panel dashboard) only shows the error of a job that was dead-lettered; a retried attempt that later succeeded no longer leaves an error behind (#75).

Full changelog: CHANGELOG · v0.4.3...v0.5.1