Show HN: BodyCommit – movement breaks in VS Code while your agent works
Develop against the extension host with Run BodyCommit in the debugger (F5). That compiles first.
以下正文同步自 Hacker News 最新,版权归原站所有,已转换为易读排版。
Develop against the extension host with Run BodyCommit in the debugger (F5). That compiles first.
Nothing here talks to an agent, and nothing is inferred from prompt text. The extension only watches editor and workspace events already available to any VS Code extension, keeps a few seconds of them in memory, and throws them away. Turn the whole thing off with BodyCommit › Agent Detection: Enabled.
A signal is active when any one of these is true. Two at once raises confidence. Thresholds are settings.
If a break is already due, an active signal is the preferred moment to show it, including the wording (“Your agent is busy writing code…” versus a plain long-session note). If Early Prompt Minutes is above 0 (default 25), an active signal can offer a break before the full interval. Set it to 0 to keep reminders on the interval only. Early prompts still wait until you are not typing.
This will sometimes be wrong. Formatters, watch scripts, and multi-file refactors can look like an agent. A terminal command only shows up when shell integration is enabled. The cost of a miss is a later reminder, not a popup on top of your typing. If the nudges feel early, turn detection off or raise the thresholds.
bodycommit.agentWait.enabled (default on) is a separate, stricter offer. It fires only when you have not typed for 8 seconds and a known agent CLI (claude, codex, aider, gemini, cursor-agent, goose, opencode, copilot) has been running in the integrated terminal for at least 35 seconds, or non-user edits have spanned at least 35 seconds with one still fresh. It still waits out the reminder interval or 15 minutes, whichever is shorter, and quiet hours, snooze, and do-not-disturb still win. A long npm test does not count. Copilot agent mode and Cursor Composer have no public “agent is running” event, so those are inferred from edits only, and a silent thinking stretch is invisible.
Agent-wait decisions are written to the BodyCommit output channel whenever they change. The older burst heuristic is logged there only when bodycommit.debug is on. The log stays on your machine.
正文由 探How 从来源站点 RSS 同步,内容未经改写;遇到排版缺失或需要图片、视频时请以原文为准。