Also in this release

MemHub
Features2
  • Rulebook controls — added support for final gates that an agent cannot override and ask rules that request approval before a matching call. Final-gate settings require an organization admin. Enforcement requires a compatible plugin: 0.152.0 or later for final gates and 0.154.0 or later for ask mode; older plugins receive advice instead.
  • Rules for more calls — rules can target MCP tools, web fetches and searches, and subagent launches, with matching output rules for their responses. These triggers require plugin 0.155.0 or later; this release adds server support without upgrading installed plugins.
Improvements2
  • Privacy information — public English/French privacy and cookie policies and a legal notice explain data handling, retention, and international transfers. Account settings link to privacy information and Cookie settings, and chat reminds users to check AI-generated answers.
  • Runtime libraries — refreshed the backend libraries used for API requests, scheduled jobs, AI provider calls, AWS access, email delivery, and PDF processing.
Fixes2
  • Consent in open tabs — cookie consent and tracker expiry now take effect while a tab stays open. Expired consent stops tracking and requests a fresh choice without requiring a reload.
  • Complexity evidence — code-complexity excerpts now focus on decision-making code inside a function, preferring changed branches over signatures and docstrings wherever those excerpts appear in PR analysis.
Security3
  • Dependency security fixes — upgraded FastAPI to 0.164.0, dateparser to 1.5.1, and pypdf to 7.1.1. These patch denial-of-service flaws in request-parameter and date parsing, plus excessive memory use and limit handling in crafted PDFs. The updates cover API requests, date extraction during URL ingestion, and PDF processing.
  • Support access — internal support can inspect a member's view in an explicitly marked read-only session. Impersonated requests are audited and changes are blocked.
  • Rulebook records — fire records from compatible plugins now carry verified chain status, making gaps and mismatches visible to the backend without rejecting older unchained clients. Backend-only contract and fire-chain ledgers also receive explicit database access protections.