rewind

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Rewind

Rewind

Use Clips Rewind as local screen memory. Start broad enough to find the right moment, then read only the smallest relevant range.
使用Clips Rewind作为本地屏幕记忆工具。先从宽泛范围入手找到正确时刻,再仅读取最小的相关区间。

First-Run Setup

首次运行设置

Call
screen_memory_status
before assuming Rewind is ready. If the tool is unavailable, do not stop at a missing-tool error and do not silently install anything:
  1. Explain that Rewind requires the signed Clips Desktop app on macOS plus a local agent connection.
  2. Ask whether Clips is installed, or use a non-mutating native application lookup when the host supports one. Do not inspect Clips' app-data folders. If Clips is absent or its presence cannot be confirmed, ask permission before opening or downloading anything: “Clips Desktop is required for Rewind. Would you like me to open the official installer and guide you through setup?”
  3. Only after affirmative permission, open
    https://clips.agent-native.com/download
    in the user's browser. Complete native installation steps only when the current host can safely do so and the user explicitly permitted them. Never bypass Gatekeeper, accept macOS permission prompts, or enable screen/audio capture on the user's behalf.
  4. If native UI control is unavailable, return the download link and wait for the user to confirm that Clips is installed and running.
  5. Ask the user to enable Rewind in the Clips tray and choose the intended capture mode. Then configure the local connection with:
    npx -y @agent-native/core@latest skills add rewind --client <client> --scope user --yes
    Replace
    <client>
    with the current compatible host:
    codex
    ,
    claude-code
    ,
    cursor
    ,
    opencode
    ,
    github-copilot
    , or
    cowork
    .
  6. Restart the host only if it cannot reload MCP servers in place, then retry
    screen_memory_status
    . Do not claim setup succeeded until it reports Rewind enabled and unpaused.
在假设Rewind已就绪前,先调用
screen_memory_status
。若工具不可用,不要停留在工具缺失的错误上,也不要静默安装任何内容:
  1. 说明Rewind需要macOS上签名的Clips Desktop应用程序,以及本地Agent连接。
  2. 询问用户是否已安装Clips,或者在主机支持的情况下使用非修改型原生应用程序查找功能。不要检查Clips的应用数据文件夹。若未安装Clips或无法确认其存在,在打开或下载任何内容前需征得许可:“Rewind需要Clips Desktop。是否需要我打开官方安装程序并引导您完成设置?”
  3. 仅在获得用户肯定许可后,在用户浏览器中打开
    https://clips.agent-native.com/download
    。仅当当前主机可安全执行且用户明确允许时,才完成原生安装步骤。绝不要绕过Gatekeeper、接受macOS权限提示,或代用户启用屏幕/音频捕获。
  4. 若无法控制原生UI,返回下载链接并等待用户确认Clips已安装并运行。
  5. 请用户在Clips托盘里启用Rewind并选择所需的捕获模式。然后使用以下命令配置本地连接:
    npx -y @agent-native/core@latest skills add rewind --client <client> --scope user --yes
    <client>
    替换为当前兼容的主机:
    codex
    claude-code
    cursor
    opencode
    github-copilot
    cowork
  6. 仅当主机无法原地重新加载MCP服务器时,才重启主机,然后重试
    screen_memory_status
    。在其报告Rewind已启用且未暂停前,不要声称设置已成功。

Retrieval Flow

检索流程

  1. Call
    screen_memory_status
    first. If the newest segment is still open, wait for it to finalize rather than substituting an older segment.
  2. Search
    screen_memory_search_chapters
    before requesting raw recent context. Use the user's words, the visible app or project, and the likely time range as clues.
  3. If several chapters plausibly match, show the candidates and ask which one the user means. Do not blend separate workstreams together.
  4. Read the smallest useful range with
    screen_memory_recent_context
    . Restate what you recovered before acting, and flag transcription or coverage uncertainty.
  5. Use
    screen_memory_frame_at
    for one exact visual moment or
    screen_memory_contact_sheet
    to scan a bounded range. Prefer local frames before escalating to cloud processing.
  6. Request the smallest relevant timestamp range through Clips' bounded private Clip handoff only when local text and frames are insufficient, such as garbled speech, important motion, dense analysis, or a Clip the user wants to keep and query later.
  1. 先调用
    screen_memory_status
    。若最新片段仍处于打开状态,等待其完成处理,不要用旧片段替代。
  2. 在请求原始最近上下文前,先调用
    screen_memory_search_chapters
    。将用户的表述、可见的应用程序或项目,以及可能的时间范围作为线索。
  3. 若有多个章节看似匹配,展示候选内容并询问用户所指的是哪一个。不要将不同的工作流混在一起。
  4. 使用
    screen_memory_recent_context
    读取最小的有用区间。在执行操作前重述所恢复的内容,并标注转录或覆盖范围的不确定性。
  5. 使用
    screen_memory_frame_at
    获取某个精确的视觉时刻,或使用
    screen_memory_contact_sheet
    扫描一个限定区间。优先使用本地帧,之后再升级到云处理。
  6. 仅当本地文本和帧不足以满足需求时(如语音混乱、重要动态、密集分析,或用户想要保存并后续查询的Clip),才通过Clips的受限私有Clip传递请求最小的相关时间戳范围。

Boundaries

边界限制

  • Rewind recordings, screenshots, audio, transcripts, OCR, and indexes remain local unless the user explicitly asks for a bounded Clip handoff.
  • Do not reveal archive filesystem paths, crawl Clips' app-data folders, or bypass the Screen Memory MCP broker.
  • Do not upload frames returned by local Screen Memory tools.
  • Treat foreground apps and chapter labels as evidence, not proof of intent.
  • If Clips is installed and Rewind is enabled but the Screen Memory MCP is missing, explain that only the agent connection needs repair with:
    npx -y @agent-native/core@latest skills add rewind --client <client> --scope user --yes
    Ask the user to restart the host if it cannot reload MCP servers in place.
  • Never conflate installing Clips Desktop with installing the skill/MCP connection, and never claim either succeeded without direct evidence.
  • Rewind的录制内容、截图、音频、转录文本、OCR和索引均保留在本地,除非用户明确要求进行受限的Clip传递。
  • 不要泄露归档文件系统路径、爬取Clips的应用数据文件夹,或绕过Screen Memory MCP代理。
  • 不要上传本地Screen Memory工具返回的帧。
  • 将前台应用程序和章节标签视为证据,而非意图的证明。
  • 若已安装Clips且Rewind已启用,但Screen Memory MCP缺失,说明只需修复Agent连接,使用以下命令:
    npx -y @agent-native/core@latest skills add rewind --client <client> --scope user --yes
    若主机无法原地重新加载MCP服务器,请用户重启主机。
  • 绝不要将安装Clips Desktop与安装技能/MCP连接混为一谈,且在没有直接证据的情况下,不要声称两者任一已成功。