Repository navigation
feat: integrate Computer History and Computer Use - #371
Merged
ZongYue99 merged 2 commits intoSep 8, 2026
Merged
Conversation
Synthetic checkpoint for safe three-way migration onto upstream computer_use; source worktree remains untouched.
Include recording, summarization, workflow extraction, replay scripts, schema, and demo fixtures.
memory-lee
requested review from
Wang-Daoji,
ZongYue99 and
wustzdy
as code owners
September 7, 2026 08:18
ZongYue99
pushed a commit
that referenced
this pull request
Sep 11, 2026
…null
Narration resolved its model with `llmRuntime(modelPreset ?? null)`. That turns
"no preset was asked for" into "resolve the preset called null", which the
gateway's resolver cannot do — it answered model_selection_unavailable, and
every summary silently kept its mechanical title.
Reproduced against the real config: llmRuntime() resolves gpt-5.6-terra,
llmRuntime("computer-use-fast") resolves it too, and only llmRuntime(null)
throws. Pass nothing when there is nothing to pass.
End to end on a real segment, 424 events compact to 56 activity arcs and come
back as "Computer History Integration Review" with an account naming DingTalk,
Arc, PR #371 and the architecture docs — instead of "用户在「Computer History
2026-09-08T08-20-00Z」中完成了一组电脑操作".
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Memtensor-AI
pushed a commit
that referenced
this pull request
Sep 15, 2026
…null
Narration resolved its model with `llmRuntime(modelPreset ?? null)`. That turns
"no preset was asked for" into "resolve the preset called null", which the
gateway's resolver cannot do — it answered model_selection_unavailable, and
every summary silently kept its mechanical title.
Reproduced against the real config: llmRuntime() resolves gpt-5.6-terra,
llmRuntime("computer-use-fast") resolves it too, and only llmRuntime(null)
throws. Pass nothing when there is nothing to pass.
End to end on a real segment, 424 events compact to 56 activity arcs and come
back as "Computer History Integration Review" with an account naming DingTalk,
Arc, PR #371 and the architecture docs — instead of "用户在「Computer History
2026-09-08T08-20-00Z」中完成了一组电脑操作".
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
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.
当前实现
本 PR 将 Computer History 和 Computer Use 集成到现有 Memmy 分支中,当前实现基于用户显式启动和停止的 macOS 操作录制。
已实现功能
Computer History 录制的是操作事件流(event stream),不是屏幕录制,也不录音。
CGEventTap和Accessibility API。--no-screenshots,没有音频采集逻辑。每次录制会将原始事件写入
events.jsonl。summarize-history.mjs生成。History 和 Workflow 分层保存。
新增
computer_historyAgent Tool,支持:正式 Workflow 是语义状态机,不是坐标宏。
Computer Use 执行路径:
mcp_open_computer_use_*;内置computer_*仅作为 fallback。原始录制数据设置 48 小时保留策略。
~/.memmy/computer-history/recordings/下的 raw recording。当前局限性
当前不是长期运行的 background service。
当前一次录制只生成一个持续更新的 History。
查询主要基于 Markdown。
events.jsonl生成。录制中的 History 不能直接生成 captured replay Workflow。
incomplete。completed后才能稳定生成 Workflow。48 小时清理目前是顺带清理。
events.jsonl。