Repository navigation
修复：复用占用 18960 端口的兼容 Memory 服务 - #600
Merged
origami-chen merged 13 commits intoOct 13, 2026
Merged
Conversation
…mand
A turn routed as end_topic used to be dropped from L1 capture as a whole,
so feedback, work conventions and instructions sent together with the
closing words never reached L1, user memory or the episode reward.
Only a bare end-topic command ("结束会话" / "不聊了") is still kept out of
L1. Every other end_topic turn now goes through the same capture decision
as a normal turn; the closed episode waits for that decision before
reflection and reward are queued.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Every memmy-memory run reports memmy_cli_* events to the cloud analytics endpoint. resolveCommandIdentity took the second positional word as command_action unconditionally, which was meant for subcommands such as `session close`. For search, add, get and delete that word is the search query, the memory text or the memory id, so it was sent verbatim. An unrecognized first word was also sent verbatim as command_group. command_action is now reported only when the first word is a group with subcommands (service, session, turn, raw) and the second word is one of that group's known subcommands; raw methods match case-insensitively, as runRaw does. An unrecognized first word is reported as command_group "unknown". The known commands live in a small table in analytics.ts that mirrors runCommand and mapTopLevelCommand. has_session_id and has_turn_id are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The session close route only woke the auto worker when the close result listed closed episodes, jobs, or scheduled evolution. For an L3 World Model v2 session, closeSession also freezes the pending L3 evidence batches and queues l3_world_model_update jobs, but it does not return them. When the session's episode had already closed earlier (idle timeout or end_topic), closedEpisodeIds was empty and nothing woke the worker. The worker does not poll, so the new L3 jobs stayed queued until an unrelated request happened to wake it. The close route now always schedules the worker, as the token compaction boundary already does after freezing batches. A close with no follow-up work costs one empty drain. A new REST contract test closes an L3 v2 session whose episode had already ended and checks that the worker picks up the frozen L3 job. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…-worker fix(memory): wake the worker after every session close
v1.2.2 requires the turn capture decision to return a non-empty l1.title together with l1.summary. The mixed feedback-and-closing test stub only returned a summary, so the capture decision threw and the closing L1 stayed in resolving instead of being activated. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…and-action fix(memory): stop sending CLI arguments as analytics command actions
fix(memory): stop dropping end-topic turns that carry feedback from L1
Synchronize the latest code from the main branch to v1.2.2
…-format fix: 兼容 LM Studio 的 JSON 响应格式
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
问题说明
通过
dev-start启动 Memmy 后，Memory 服务已经监听 18960 端口。此时再打开打包版，如果现有 Memory 服务因模型异常而在健康接口中返回ok: false，桌面端会将其误判为未知服务，并尝试在同一端口启动第二个 Memory 进程，最终提示端口被占用、记忆服务不可用。修复内容
dev-start服务返回降级健康状态，并验证桌面端不会创建第二个 Memory 子进程。验证结果
npm exec -w @memmy/desktop -- vitest run tests/runtime-services.test.ts：57 项通过npm run typecheck -w @memmy/desktop：通过npm run package:mac:arm64:cn:unsigned：通过hdiutil verify App/shell/desktop/release/Memmy-1.2.1-darwin-arm64-cn-unsigned.dmg：通过