1.4.0

v1.4.0

中文

对话更可靠，知识维护更安全： v1.4.0 让普通对话和知识库对话在存储迁移、上下文变化、插件重载或切换 Agent 后继续使用同一份可恢复历史；知识维护也会先隔离和校验成果，再写入 Vault。

对话生命周期升级

• 旧的普通对话和知识库对话会自动迁移，并保留消息、工作区边界和可恢复的 Agent 连接状态。
• 新建空白对话、已有普通对话和知识库直接对话都能正常保存，插件重载后可继续使用。
• 对话线程、单轮执行和 Agent 原生会话使用明确身份，减少恢复时的冲突和错误串线。

更安全的知识维护

• /maintain 默认使用启动时选中的 Agent；只有失败尝试已安全隔离且没有可提交成果时，才尝试备用 Agent。
• 维护成果先在隔离环境中验证，再通过可恢复提交写入 Vault；超时、重载或部分失败不会重复提交同一成果。
• 大文件、无变化来源和恢复中的任务会显示准确状态，不再被误标为已提炼或普通失败。
• 维护阶段进度和最终报告更容易看懂；报告可以稳定展开和收起，引用的 Vault 笔记可以直接点击打开。
• 修复维护报告执行详情导致的“实时对话与持久记录不一致”；后台定时维护也不再向正在使用的对话追加消息。
• 只有明确可重试的定时失败才会再次运行，当天最多 3 次，分别等待 5 分钟和 15 分钟，不再每分钟重复失败。
• EchoInk 启动 Codex 时会关闭全局 Hook 和全局 Memory 注入，避免维护 Shadow 被外部记忆系统接管；插件自己的 .echoink/memory 不受影响。
• 修复 Obsidian 自动更新 updated 字段恰好撞上维护事务写入时，合法事务硬链接被误判为外部篡改、导致恢复受阻的问题；真正的额外硬链接仍会阻断提交。

记录与会话管理

• 对话历史、工作流运行、业务成果和 Agent 原生会话使用独立的保留、恢复与清理规则。
• 新增紧凑会话选择器，支持搜索、键盘导航和批量管理，同时保护知识库频道与运行中的会话。
• 清理操作先生成可恢复计划和证据，再执行实际变更，降低误删或半完成状态的风险。

使用方法

1. 安装 v1.4.0 并重载 Obsidian。现有对话会在需要时自动升级，不需要手动迁移。
2. 打开新对话或已有对话；普通对话按提示选择工作区，知识库频道继续使用当前 Vault。
3. 在知识库频道运行 /check 或 /maintain，通过阶段进度查看当前状态，完成后展开报告并点击来源笔记核对结果。
4. 通过顶部会话入口搜索或管理已有对话；运行中的会话和知识库频道不会被批量删除。

现有 Vault 笔记和 EchoInk 会话不需要重置。旧版 Native Execution 清理警告仍可能出现在少量历史数据上，但不会改变已经保存的对话或业务成果。

下载

Obsidian 官方安装会读取本 Release 下的单文件资产：main.js、manifest.json、styles.css。

English

More durable conversations and safer Knowledge maintenance: v1.4.0 keeps Chat and Knowledge conversations on one recoverable history across storage migration, context changes, plugin reloads, and Agent switches. Knowledge maintenance now isolates and validates output before it reaches the Vault.

Conversation lifecycle upgrade

• Existing Chat and Knowledge conversations migrate automatically while preserving messages, workspace boundaries, and recoverable Agent bindings.
• New blank chats, existing Chat sessions, and direct Knowledge conversations can all be saved and continued after a plugin reload.
• Conversation threads, individual turns, and native Agent sessions use distinct identities, reducing recovery conflicts and cross-session mix-ups.

Safer Knowledge maintenance

• /maintain starts with the selected Agent and tries a fallback only when the failed attempt is safely isolated and contains no committable result.
• Maintenance output is validated in isolation before a recoverable commit reaches the Vault. Timeouts, reloads, and partial failures do not commit the same result twice.
• Oversized sources, unchanged inputs, and recovering tasks now receive accurate states instead of being marked as processed or reduced to generic failures.
• Maintenance progress and final reports are easier to follow. Reports expand and collapse reliably, and referenced Vault notes open directly for verification.
• Fixed execution diagnostics being mistaken for a divergence between the live conversation and its durable record. Scheduled maintenance also stops appending background messages to active conversations.
• Only explicitly retryable scheduled failures run again, with at most three daily attempts after 5- and 15-minute delays instead of retrying every minute.
• EchoInk disables global hooks and global memory injection for the Codex processes it launches, preventing external memory layers from taking over maintenance Shadows. EchoInk's own .echoink/memory remains unchanged.
• Fixed recovery being blocked when Obsidian updated the updated field during a maintenance transaction and the expected install hardlink was mistaken for external tampering. A genuine additional hardlink still blocks the commit.

Record and session management

• Conversation history, workflow runs, business artifacts, and native Agent sessions follow separate retention, recovery, and cleanup rules.
• A compact session picker adds search, keyboard navigation, and batch management while protecting the Knowledge channel and running sessions.
• Cleanup operations produce a recoverable plan and evidence before applying changes, reducing accidental deletion and half-finished states.

How to use

1. Install v1.4.0 and reload Obsidian. Existing conversations upgrade automatically when needed; no manual migration is required.
2. Open a new or existing conversation. Select a workspace for regular Chat when prompted; the Knowledge channel continues to use the current Vault.
3. Run /check or /maintain in Knowledge, follow the stage progress, then expand the report and open referenced notes to verify the result.
4. Use the session entry in the header to search or manage existing conversations. Running sessions and the Knowledge channel are protected from batch deletion.

Existing Vault notes and EchoInk conversations do not require a reset. Legacy Native Execution cleanup warnings may still appear for a small amount of historical data, but they do not change saved conversations or business results.

Download

Obsidian reads these single-file Release assets directly: main.js, manifest.json, and styles.css.