MemoryBear v0.3.3 Community Release Note

[keeees]

MemoryBear v0.3.3 Community Release Notes — Expanding Realms

Release Date: May 14, 2026 | Codename: YanJing (衍境 · Expanding Realms)

MemoryBear v0.3.3 Community delivers a comprehensive set of upgrades to memory intelligence, knowledge base management, and workflow orchestration. This release introduces temporal retrieval for memory entities, a revamped extraction pipeline, full single-node workflow execution, and significant knowledge base enhancements — alongside a broad set of stability fixes across the platform.

---

🚀 I. Core Upgrade Overview

1. Memory Intelligence 🧠

• Dashboard End-User Filtering: The dashboard/end_users endpoint now filters out users with zero memory entries, keeping the dashboard focused on active memory profiles.
• New Extraction Pipeline: Switched to the new memory extraction pipeline, delivering improved accuracy and throughput for entity and relationship extraction.
• Ontology Upper/Lower Level Update: Updated the universal ontology engineering definitions for upper and lower levels, resulting in more accurate entity and relationship category extraction.
• Metadata Display Enhancement: The /memory-storage/end_user_info endpoint now surfaces only the most relevant user profile fields: goals, traits, interests, and core_facts.
• Alias Extraction Improvement: Aliases are now extracted during node merging when alias relationships exist, ensuring alias information stays current as the knowledge graph evolves.
• Temporal Fields for Entity Relations: Entity relationships now carry three time fields — dialog_at (conversation time), valid_at (event occurrence time), and invalid_at (event expiration time) — enabling precise temporal reasoning.
• L0 Memory Read Enhancement: Memory reads now return fixed user alias and user description fields (goals, traits, interests, core_facts) as part of the L0 response.
• Temporal Retrieval (valid_at): Statements can now be retrieved by valid_at event occurrence time, enabling time-based memory queries such as "what happened last week."
• Memory Validation Session Support: The memory validation endpoint now accepts session_id and removes the history parameter, enabling proper coreference resolution across conversation turns.
• Knowledge Base Custom Prompt for QA Extraction: Mind-map knowledge base QA pair extraction now supports custom prompt input — uses system prompt when empty, custom prompt when provided.

---

2. Knowledge Base Integration 📚

• CSV Tabular Import Logic: CSV file imports now follow a one-QA-pair-per-chunk model, where each row of question-answer data generates an independent chunk for precise retrieval.
• Manual QA Chunk Fix: Fixed the issue where manually creating a knowledge entry with QA extraction would generate duplicate entries; added chunk deletion support (with graph rebuild trigger button).
• Visible IDs on Knowledge Page: Knowledge base pages now display knowledge base ID, document ID, and chunk ID for easier debugging and cross-referencing.
• File System Abstraction: Knowledge base file storage now uses the API-level file system, supporting OSS, S3, and local storage backends interchangeably.
• Batch Operations API: Added server-side batch operation APIs for knowledge base entry management, enabling bulk imports and modifications.

---

3. Workflow & Application ⚙️

• Single-Node Execution Phase 1: Workflows now support running individual nodes in isolation — covering Model and Tool node types for rapid testing and debugging.
• Single-Node Execution Phase 2: Extended single-node execution to all remaining node types: Code Execution, HTTP Request, Memory Read, Knowledge Retrieval, Memory Storage, Parameter Extraction, Document Extractor, List Operations, Template Rendering, Question Classifier, Iteration, Loop, Variable Aggregation, Variable Assignment, and Conditional Branch.
• Variable Real-Value Display: Node inputs containing variables now display their resolved real values instead of variable names in the node visualization panel.
• Model Node Exception Branch: Model nodes now include an exception handling branch to gracefully handle sensitive word filtering errors instead of failing silently.
• OpenAI Channel Tool Parameter Fix: Fixed the Agent OpenAI channel tool parameter passing issue caused by model gateway provider misconfiguration (provider incorrectly set to openai for gateway-sourced models).

---

4. Frontend & UX 🎨

• Safari Workflow Support: Workflow editor now fully supports Safari browser, resolving rendering and interaction issues specific to WebKit.
• Login Page UI Redesign: Completely redesigned the login page with a modern, streamlined interface.

---

5. Robustness & Bug Fixes 🔧

• Multi-Space Member Login (Chrome): Fixed an issue where members belonging to multiple spaces could not access the login page on Chrome.
• Workflow Share Node Error Interaction: Improved error handling for the workflow experience-sharing node to display proper error feedback instead of failing silently. (In Progress)
• Hybrid Retrieval Threshold Mismatch: Resolved inconsistency between the knowledge base recall test's similarity thresholds and the workflow knowledge retrieval node's vector similarity thresholds.
• Vector Similarity Weight Drift: Fixed an issue where vector_similarity_weight would change unexpectedly during speech library testing with the knowledge retrieval node in 400-inbound call workflows.
• Reranker Model Config Failure: Fixed the knowledge retrieval node's global configuration where the Reranker model selector would fail to open.
• JSON Output Toggle Reset: Fixed a bug where selecting a JSON-output model, enabling the JSON toggle, clicking away, and clicking back would reset the toggle — and saving would not persist the setting.
• Search Mode Parameter Leakage: Fixed an issue where switching from hybrid search to keyword or semantic search would retain both similarity_threshold and vector_similarity_weight parameters, even though only one applies to the selected mode.
• Memory Read Validation Error: Fixed the deep-thinking mode memory extraction error where asking "who am I" caused a Pydantic validation failure (string_type expected but received list input ['用户是谁']).
• HTTP Request Streaming Error: Fixed the HTTP request node exception "Attempted to access streaming request content, without having called read()" by properly handling streaming response bodies.

---

🧭 Looking Ahead

MemoryBear v0.3.3 represents a significant step toward production-grade memory intelligence. The introduction of temporal fields, enhanced extraction pipelines, and L0 memory enrichment collectively transform MemoryBear from a memory store into a temporally-aware reasoning substrate — one that understands not just what happened, but when it happened and when it stopped being true.

The workflow single-node execution capability marks a turning point for developer experience. By enabling isolated testing of every node type, we dramatically reduce the iteration cycle for complex workflow development. Combined with real-value variable display, this release makes MemoryBear workflows significantly more debuggable and portable.

The next version will focus on a comprehensive upgrade of the memory engine's core capabilities, completing application interaction and Agent/workflow features, optimizing knowledge base and frontend iframe multimodal support, introducing SSO/OIDC integration interfaces, and resolving remaining known issues across the platform.

---

---

MemoryBear v0.3.3 社区版 发布说明 —— 衍境

发布日期： 2026年5月14日 ｜ 版本代号： 衍境（YanJing · Expanding Realms）

MemoryBear v0.3.3 社区版对记忆智能、知识库管理和工作流编排进行了全面升级。本版本引入了记忆实体的时间检索能力、全新萃取流水线、完整的工作流单节点执行支持以及多项知识库增强，同时修复了平台中大量稳定性问题。

---

🚀 一、核心升级概览

1. 记忆智能 🧠

• Dashboard 用户过滤：dashboard/end_users 接口现在会过滤记忆数为 0 的用户，保持仪表盘聚焦于活跃记忆档案。
• 切换新萃取流水线：切换至新一代记忆萃取流水线，提升实体和关系提取的准确率与吞吐量。
• 本体工程 Upper/Lower Level 更新：更新通用本体工程的上下层级定义，现在能提取到更准确的实体/关系类别。
• Metadata 内容展示增强：/memory-storage/end_user_info 接口现在只展示最相关的用户画像字段：goals、traits、interests、core_facts。
• 别名提取改进：现在会在有别名关系的节点合并时自动提取别名，确保知识图谱演进过程中别名信息保持最新。
• 实体关系时间字段：实体关系新增三个时间字段——dialog_at（对话发生时间）、valid_at（事件发生时间）、invalid_at（事件失效时间），支持精确的时间推理。
• L0 记忆读取增强：记忆读取时现在会返回固定的用户别名和用户描述字段（goals、traits、interests、core_facts）。
• 时间检索（valid_at）：现在可以通过 valid_at 事件发生时间检索 statement 句子，支持"上周发生了什么"等时间维度查询。
• 记忆验证 Session 支持：记忆验证接口新增 session_id 参数，去除 history 参数，以支持跨对话轮次的代词消融。
• 知识库自定义提示词 QA 提取：脑图知识库问答对提取支持自定义提示词输入——未填写时采用系统提示词，填写则采用自定义提示词。

---

2. 知识库集成 📚

• CSV 表格导入逻辑：CSV 文件导入后按一条 QA 对应一个分块（chunk）的方式处理，即一行问答数据生成一个独立分块，确保检索精度。
• 手动 QA 分块修复：修复手动创建知识选择问答对提取会生成两条的问题；支持删除分块（删除后需重建图谱，增加了操作按钮）。
• 知识库页面 ID 展示：知识库页面现在显示知识库 ID、文档 ID 和 chunk ID，方便调试和交叉引用。
• 文件系统抽象：知识库文件存储使用 API 层文件系统，支持 OSS、S3 和本地存储后端互换。
• 批量操作 API：新增知识库录入的服务端批量操作 API，支持批量导入和修改。

---

3. 工作流与应用 ⚙️

• 单节点运行（第一阶段）：工作流支持单独运行模型节点和工具节点，实现快速测试和调试。
• 单节点运行（第二阶段）：扩展单节点执行至所有剩余节点类型：代码执行、HTTP 请求、记忆提取、知识检索、记忆存储、参数提取、文档提取器、列表操作、模版渲染、问题分类器、迭代、循环、变量聚合、变量赋值、条件分支。
• 变量真实值展示：节点输入中包含变量时，现在展示解析后的真实值而非变量名称。
• 模型节点异常处理分支：模型节点新增异常处理分支，优雅处理敏感词过滤等错误，避免静默失败。
• OpenAI 通道工具传参修复：修复 Agent OpenAI 通道工具传参问题，原因是模型网关来源的模型 provider 被错误设置为 openai。

---

4. 前端与用户体验 🎨

• Safari 工作流支持：工作流编辑器全面支持 Safari 浏览器，解决 WebKit 特有的渲染和交互问题。
• 登录页 UI 改版：全新设计的登录页面，界面更加现代简洁。

---

5. 稳定性与缺陷修复 🔧

• 多空间成员登录（Chrome）：修复属于多个空间的成员无法在 Chrome 上访问登录页面的问题。
• 工作流分享节点报错交互：改进工作流体验分享节点的错误处理，显示正确的错误反馈。（开发中）
• 混合检索阈值不匹配：解决知识库召回测试中相似度阈值与工作流知识检索节点中向量相似度阈值不一致的问题。
• 向量相似度权重漂移：修复 400 呼入话术库测试时知识检索节点 vector_similarity_weight 意外变化的问题。
• Reranker 模型配置失败：修复知识检索节点全局配置中 Reranker 模型选择器无法打开的问题。
• JSON 输出开关重置：修复选择带 JSON 输出的模型、打开 JSON 开关后，点击空白区域再点回节点时开关被重置且保存不生效的问题。
• 检索模式参数泄漏：修复从混合检索切换为分词检索或语义检索时，similarity_threshold 和 vector_similarity_weight 两个参数同时存在的问题（实际上单一检索模式只需其中一个）。
• 记忆读取验证错误：修复深度思考模式下询问"我是谁"时记忆提取节点报 Pydantic 验证错误的问题（期望 string 类型但收到 list 类型 ['用户是谁']）。
• HTTP 请求流式错误：修复 HTTP 请求节点异常"Attempted to access streaming request content, without having called read()"，正确处理流式响应体。

---

🧭 未来展望

MemoryBear v0.3.3 标志着向生产级记忆智能迈出的重要一步。时间字段的引入、萃取流水线的升级以及 L0 记忆丰富化，共同将 MemoryBear 从一个记忆存储系统转变为具备时间感知能力的推理基座——它不仅理解发生了什么，还理解何时发生、何时失效。

工作流单节点执行能力是开发者体验的一个转折点。通过支持所有节点类型的独立测试，我们大幅缩短了复杂工作流开发的迭代周期。结合变量真实值展示，本版本让 MemoryBear 工作流变得更加可调试、可移植。

下一版本将重点全面升级记忆引擎核心能力，补齐应用交互与 Agent/工作流功能，优化知识库与前端 iframe 多模态支持，并修复各类现存问题。

---

This discussion was created from the release MemoryBear v0.3.3 Community Release Note.