agentation-watch-mode
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseAgentation watch mode
Agentation 监听模式
When to use: The user says , wants continuous Agentation feedback handling, or asks you to keep watching annotations and applying fixes as new feedback arrives.
watch mode适用场景: 用户提及、需要持续处理Agentation反馈,或要求你持续监听标注并在收到新反馈时应用修复。
watch modeGoal
目标
Stay in a watch loop so the user can annotate in the browser and have those annotations processed continuously.
保持监听循环状态,以便用户可在浏览器中进行标注,且这些标注能得到持续处理。
Workflow
工作流程
- Start a watch loop with .
agentation_agentation_watch_annotations - For each returned annotation:
- Call immediately so the user can see you picked it up.
agentation_agentation_acknowledge - Read any extra session context you need.
- Make the requested fix.
- Call with a short summary of what changed.
agentation_agentation_resolve
- Call
- After the batch is done, call again.
agentation_agentation_watch_annotations - Continue until the user says stop or the watch call times out.
- 调用启动监听循环。
agentation_agentation_watch_annotations - 对于每个返回的标注:
- 立即调用,让用户看到你已接收该标注。
agentation_agentation_acknowledge - 读取所需的额外会话上下文。
- 执行请求的修复操作。
- 调用并附上变更内容的简短摘要。
agentation_agentation_resolve
- 立即调用
- 批次处理完成后,再次调用。
agentation_agentation_watch_annotations - 持续执行直到用户要求停止或监听调用超时。
Defaults
默认设置
- If the user gives a session ID, watch that session.
- If they do not, watch all sessions.
- Use a short batching window so nearby annotations are grouped together.
- Use a reasonable timeout and report when it expires.
- 若用户提供会话ID,则监听该会话。
- 若未提供,则监听所有会话。
- 使用较短的批处理窗口,以便将相近的标注分组处理。
- 设置合理的超时时间,并在超时后进行报告。
Handling ambiguous feedback
模糊反馈处理
- If an annotation is unclear, reply on the thread with a short clarifying question before making speculative changes.
- If you cannot complete the fix safely, leave the annotation open and explain the blocker in a reply.
- 若标注内容不明确,先在线程中回复简短的澄清问题,再进行推测性修改。
- 若无法安全完成修复,保持标注为未处理状态,并在回复中说明阻碍原因。
Response style
响应风格
- Keep progress updates brief.
- In each resolve summary, state what you changed, not just that it is done.
- 进度更新保持简洁。
- 在每个修复摘要中说明具体变更内容,而非仅告知已完成。