[Bug][Kimi Desktop] "chat 记忆 / 梦境记忆"开关拨动后不写入配置；疑似服务端功能门控未放行 || [Bug][Kimi Desktop] "chat memory / The configuration of "Dream Memory" is not written after the switch is toggled; it is suspected that the server function gate control is not released.

环境 / Environment

• Kimi Desktop 3.2.9（macOS，Electron 43.6.0）
• 账号：Vivace 会员；Kimi 用户 ID d4oqc48c86sb71q5v4jg；联系邮箱 mgh1996930@gmail.com

现象（Bug）/ What happens

设置 → chat 记忆 →「梦境记忆」开关可以正常拨动，但拨动后检查本地运行配置 daimon/config.json：

• features.memory、features.memory.dream、runtime.dream.autoTriggerEnabled 仍为 false；
• vault-memory 仍在 runtime.systemTools.disabled 列表中。

2026-09-17 凌晨与傍晚两次尝试（中间含完整重启客户端）均未落盘。重启时应用以内存中的旧配置回写文件，覆盖任何外部修改。设置页开关状态与本地运行配置之间存在同步断链。

In English: the Settings → Chat Memory → "Dream Memory" toggle flips in the UI but never reaches the local runtime config (daimon/config.json: features.memory, features.memory.dream, runtime.dream.autoTriggerEnabled stay false; vault-memory stays in runtime.systemTools.disabled). Two attempts on 2026-09-17 (with a full restart in between) produced no persisted change; on restart the app rewrites the config from its in-memory state, clobbering any external edit.

功能申请 / Feature request

本地存储中可见服务端下发的功能门控 n2s_memory_client = 0，疑似该账号未被纳入 chat 记忆功能名单。申请：

1. 为该账号开通 chat 记忆（含梦境记忆）功能；
2. 修复上述设置开关与本地配置之间的同步问题。

The client-side local storage shows a server-pushed feature flag n2s_memory_client = 0; this account appears to be outside the chat-memory rollout. Please (1) enable chat memory (incl. dream memory) for this account, and (2) fix the settings-to-config sync bug.

---

Environment / Environment

• Kimi Desktop 3.2.9 (macOS, Electron 43.6.0)
• Account: Vivace member; Kimi user ID d4oqc48c86sb71q5v4jg; contact email mgh1996930@gmail.com

Phenomenon (Bug) / What happens

Settings → Chat Memory → "Dream Memory" switch can be toggled normally, but after toggling it, check the local running configuration daimon/config.json:

• features.memory, features.memory.dream, runtime.dream.autoTriggerEnabled are still false;
• vault-memory is still in the runtime.systemTools.disabled list.

Two attempts in the early morning and evening of 2026-09-17 (including a complete restart of the client) failed to place the order. On restart, the application writes back the file with the old configuration in memory, overwriting any external modifications. There is a synchronization disconnection between the switch status of the settings page and the local running configuration.

In English: the Settings → Chat Memory → "Dream Memory" toggle flips in the UI but never reaches the local runtime config (daimon/config.json: features.memory, features.memory.dream, runtime.dream.autoTriggerEnabled stay false; vault-memory stays in runtime.systemTools.disabled). Two attempts on 2026-09-17 (with a full restart in between) produced no persisted change; on restart the app rewrites the config from its in-memory state, clobbering any external edit.

Feature request / Feature request

The function gate n2s_memory_client = 0 issued by the server can be seen in the local storage. It is suspected that the account has not been included in the chat memory function list. Application:

1. Activate the chat memory (including dream memory) function for this account;
2. Fix the synchronization problem between the above setting switches and local configuration.

The client-side local storage shows a server-pushed feature flag n2s_memory_client = 0; this account appears to be outside the chat-memory rollout. Please (1) enable chat memory (incl. dream memory) for this account, and (2) fix the settings-to-config sync bug.

Start by reproducing the toggle from Settings → Chat Memory and inspect daimon/config.json together with the local n2s_memory_client feature flag. Trace how the toggle maps to features.memory, features.memory.dream, runtime.dream.autoTriggerEnabled, and runtime.systemTools.disabled; done means the supported setting persists through restart, or the server-side rollout restriction is confirmed separately.