smartcompact 0.1.5 → 0.1.6

package/README.md

@@ -13,7 +13,7 @@
 
 Every request re-reads the whole context, so a long context makes every step expensive. Native auto-compaction waits until the context is nearly full (close to 1M tokens in Claude Code, up to 800k in Codex if configured), and it ignores timing, so it often lands in the middle of a task. SmartCompact works with Claude Code (CLI and desktop app), [Pi](https://github.com/earendil-works/pi) and the Codex CLI:
 
-- **Compact at a good moment.** Once the context passes the **allow line** (200k tokens by default), it compacts when a turn ends, if a piece of work has been finished since the last compaction (a commit, tests passing, a task completed).
+- **Compact at a good moment.** Once the context passes the **allow line** (200k tokens by default), it compacts when a turn ends, if a piece of work has been finished since the last compaction (a commit, tests passing, a task completed) and no file has been changed since.
 - **Never in the middle of work.** It only decides when a turn ends, never mid-turn, and it waits while tests or the build are failing or errors keep repeating.
 - **No limit of its own.** If no piece of work gets finished, the agent is usually deep in one large task, which is when a large context pays off. SmartCompact leaves it alone, and the platform's native compaction applies as it would without the plugin.
 - **A progress ledger bridges the gap.** Files changed, the latest commit and test result, and decisions the agent recorded are handed back to the model after compaction.
@@ -80,7 +80,7 @@ Codex hooks cannot postpone a compaction in the middle of a turn, so SmartCompac
 
 ## FAQ
 
-**How does it know a piece of work is finished?** From the commands the agent runs. Any finished piece of work since the last compaction counts, not only one in the current turn: the end of a turn is already a pause, so waiting for the next commit would mostly just cost more. A commit counts if `git commit` actually ran and the tool call did not fail. A test command piped into something else (`| tail`) without `pipefail` does not count, since its exit code cannot be trusted.
+**How does it know a piece of work is finished?** From the commands the agent runs. Any finished piece of work since the last compaction counts, not only one in the current turn: the end of a turn is already a pause, so waiting for the next commit would mostly just cost more. Once files are changed again after it, the next piece of work has started, and SmartCompact waits for that one to finish. A commit counts if `git commit` actually ran and the tool call did not fail. A test command piped into something else (`| tail`) without `pipefail` does not count, since its exit code cannot be trusted.
 
 **Will the model forget things after compaction?** Sometimes, for details mentioned in passing. The ledger only records files, commits, tests and decisions the model chose to record. Details the user mentions in passing are kept by asking the compaction summary to keep every specific fact the user stated. On Pi this clearly reduced losses, but it is not a guarantee.
 

package/README.zh-CN.md

@@ -13,7 +13,7 @@
 
 agent 每发一次请求，都要把整段上下文重新读一遍，上下文越长，每一步越贵。原生的自动压缩要等到快满了才触发（Claude Code 接近 100 万，Codex 可以配到 80 万），而且不看时机，常常发生在一件事做到一半的时候。SmartCompact 支持 Claude Code（终端和桌面 App）、[Pi](https://github.com/earendil-works/pi) 和 Codex 命令行：
 
-- **挑对时机压缩。** 上下文超过**允许压缩线**（默认 20 万）以后，只要上次压缩以来做完过一件事（一次提交、测试通过、任务完成），就在这一轮结束时压缩。
+- **挑对时机压缩。** 上下文超过**允许压缩线**（默认 20 万）以后，只要上次压缩以来做完过一件事（一次提交、测试通过、任务完成），之后又没开始改文件，就在这一轮结束时压缩。
 - **不在做到一半时压缩。** 只在一轮结束时判断，从不在一轮中间主动压缩；测试失败、构建失败或连续报错时先等着。
 - **不设自己的上限。** 一直没做完一件事，多半是在干一件大活，这时正需要大上下文。插件不去打断，压缩按平台原生规则来，和没装插件时一样。
 - **用进度笔记接上。** 改过的文件、最近的提交和测试结果、记下的决定，压缩后补回给模型。
@@ -80,7 +80,7 @@ Codex 的 hook 不能推迟一轮中间的压缩，所以插件在一轮结束
 
 ## 常见问题
 
-**怎么判断"做完一件事"？** 靠识别 agent 执行的命令。看的是上次压缩以来有没有做完过一件事，不要求正好在这一轮：一轮结束本身就是停顿点，非要等下一次提交，多半只是多花钱。提交只要真的执行了 `git commit` 且工具调用没报错就算；测试命令接了管道（`| tail`）又没开 `pipefail` 时退出码不可信，不算测试结果。
+**怎么判断"做完一件事"？** 靠识别 agent 执行的命令。看的是上次压缩以来有没有做完过一件事，不要求正好在这一轮：一轮结束本身就是停顿点，非要等下一次提交，多半只是多花钱。但做完之后又开始改文件，就算在做下一件事，要等它做完。提交只要真的执行了 `git commit` 且工具调用没报错就算；测试命令接了管道（`| tail`）又没开 `pipefail` 时退出码不可信，不算测试结果。
 
 **压缩后模型会不会忘事？** 随口提到的细节有时会丢。进度笔记只记文件、提交、测试和模型主动记下的决定。用户在对话里随口交代的细节，靠压缩时要求摘要原样保留用户说过的具体信息。Pi 上这样做明显减少了丢失，但不能保证不丢。
 

package/adapters/pi/recognize.ts

@@ -20,6 +20,7 @@ export function recognizePi(outcome: PiToolOutcome, ledger: Ledger): { signals:
   const { path, command } = outcome.input
   if (EDIT_TOOLS.has(outcome.toolName) && !outcome.isError && typeof path === 'string' && path) {
     next = recordFileChanged(next, path)
+    signals.push({ kind: 'file-changed' })
   }
   if (outcome.toolName === 'bash' && typeof command === 'string' && command) {
     const classified = classifyCommand(command, outcome.isError, outcome.text, next)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "smartcompact",
-  "version": "0.1.5",
+  "version": "0.1.6",
   "type": "module",
   "description": "Compact long agent sessions earlier, at a finished piece of work, to cut cost without losing results (Claude Code, pi, Codex)",
   "license": "MIT",

package/plugin/src/core/decide.ts

@@ -17,7 +17,7 @@ export type DecisionInput = {
 
 export type TurnEndDecision =
   | { action: 'none'; reason: 'paused' | 'no-reading' | 'below-line' }
-  | { action: 'wait'; reason: HardSignal | 'insufficient-benefit' | 'waiting-for-milestone' }
+  | { action: 'wait'; reason: HardSignal | 'insufficient-benefit' | 'changed-since-milestone' | 'waiting-for-milestone' }
   | { action: 'compact'; reason: MilestoneSource }
 
 export type MidTurnDecision =
@@ -36,7 +36,9 @@ export function decideAtTurnEnd(input: DecisionInput, params: Params): TurnEndDe
   const hard = hardSignal(work, params)
   if (hard) return { action: 'wait', reason: hard }
   if (!freesEnough(tokens, input, params)) return { action: 'wait', reason: 'insufficient-benefit' }
-  if (work.milestone) return { action: 'compact', reason: work.milestone }
+  if (work.milestone && !work.changedSinceMilestone) return { action: 'compact', reason: work.milestone }
+  // 做完一件事之后又改了文件，已经在做下一件事，等它做完。
+  if (work.milestone) return { action: 'wait', reason: 'changed-since-milestone' }
   // 不设兜底线：一直等不到做完一件事，多半是在做一件大活，正需要大上下文；交给原生在上限处压缩。
   return { action: 'wait', reason: 'waiting-for-milestone' }
 }

package/plugin/src/core/report.ts

@@ -1,6 +1,7 @@
 // /smartcompact report 的内容：当前状态、决策次数、信号次数、成本估算。只排版，不读写。
 
 import type { Lines } from './lines.ts'
+import type { WorkState } from './signals.ts'
 import type { DecisionLogEntry, SessionState } from './state.ts'
 import { savingsRatio } from './usage.ts'
 
@@ -18,6 +19,9 @@ export function countDecisions(entries: readonly DecisionLogEntry[]): DecisionCo
 
 const k = (tokens: number | undefined): string => (tokens === undefined ? '—' : `${Math.round(tokens / 1000)}k`)
 
+const milestoneStatus = (work: WorkState): string =>
+  !work.milestone ? '等待阶段节点' : work.changedSinceMilestone ? `上一件事已做完（${work.milestone}），之后又改了文件，等这件事做完` : `已到阶段节点（${work.milestone}）`
+
 export function renderReport(input: {
   state: SessionState
   lines: Lines
@@ -33,7 +37,7 @@ export function renderReport(input: {
     `- 本会话压缩 ${state.compactions} 次；最近一次压缩后约 ${k(state.measuredAfterTokens)}`,
     `- 本会话决策：插件压缩 ${(counts['compacted:plugin'] ?? 0) + (counts['compacted:plugin-queued'] ?? 0)}，自动压缩放行 ${counts['compacted:auto'] ?? 0}，手动压缩 ${counts['compacted:manual'] ?? 0}，轮中否决 ${counts['mid-turn:veto'] ?? 0}，轮末等待 ${counts['turn-end:wait'] ?? 0}`,
     `- 信号：提交 ${seen.commit}，测试通过 ${seen['tests-passed']}，任务完成 ${seen['task-completed']}，checkpoint 完成 ${seen.checkpoint}`,
-    `- 当前状态：${state.work.milestone ? `已到阶段节点（${state.work.milestone}）` : '等待阶段节点'}${state.work.testsFailing ? '，测试失败中' : ''}${state.work.buildFailing ? '，构建失败中' : ''}`,
+    `- 当前状态：${milestoneStatus(state.work)}${state.work.testsFailing ? '，测试失败中' : ''}${state.work.buildFailing ? '，构建失败中' : ''}`,
     ratio === undefined
       ? '- 成本估算：还没有读数'
       : `- 成本估算：上下文成本约节省 ${Math.round(ratio * 100)}%（${state.usage.samples} 次读数，已扣除压缩本身的开销；对比的是没有插件、一直涨到原生压缩点的情况）${

package/plugin/src/core/signals.ts

@@ -9,6 +9,7 @@ export type Signal =
   | { kind: 'task-completed' }
   | { kind: 'checkpoint'; milestone: boolean }
   | { kind: 'tool-result'; isError: boolean }
+  | { kind: 'file-changed' }
 
 export type MilestoneSource = 'commit' | 'tests-passed' | 'task-completed' | 'checkpoint'
 
@@ -19,6 +20,8 @@ export type WorkState = {
   milestone: MilestoneSource | null
   /** 最近的阶段节点出现时的上下文用量，用来看它到压缩时隔了多远 */
   milestoneTokens?: number
+  /** 最近的阶段节点之后又改过文件：已经开始下一件事，这个阶段节点不再算数 */
+  changedSinceMilestone?: boolean
   testsFailing: boolean
   buildFailing: boolean
   errorStreak: number
@@ -26,6 +29,7 @@ export type WorkState = {
 
 export const INITIAL_WORK_STATE: WorkState = Object.freeze({
   milestone: null,
+  changedSinceMilestone: false,
   testsFailing: false,
   buildFailing: false,
   errorStreak: 0,
@@ -50,7 +54,7 @@ export function milestoneOf(signal: Signal): MilestoneSource | null {
 export function applySignal(state: WorkState, signal: Signal): WorkState {
   const milestone = milestoneOf(signal)
   // 失败之后又做完了一件事（比如提交、checkpoint），那段失败就算过去了，不再挡着压缩。
-  const next = milestone ? { ...state, milestone, testsFailing: false, buildFailing: false } : state
+  const next = milestone ? { ...state, milestone, changedSinceMilestone: false, testsFailing: false, buildFailing: false } : state
   switch (signal.kind) {
     case 'tests':
       return { ...next, testsFailing: !signal.passed }
@@ -58,6 +62,9 @@ export function applySignal(state: WorkState, signal: Signal): WorkState {
       return { ...next, buildFailing: !signal.passed }
     case 'tool-result':
       return { ...next, errorStreak: signal.isError ? state.errorStreak + 1 : 0 }
+    // 做完一件事之后又改文件，说明已经开始下一件事，要等它做完。
+    case 'file-changed':
+      return next.milestone ? { ...next, changedSinceMilestone: true } : next
     default:
       return next
   }
@@ -65,7 +72,7 @@ export function applySignal(state: WorkState, signal: Signal): WorkState {
 
 /** 压缩后清空阶段节点；失败这些仍然成立的事实保留。 */
 export function afterCompaction(state: WorkState): WorkState {
-  return { ...state, milestone: null, milestoneTokens: undefined }
+  return { ...state, milestone: null, milestoneTokens: undefined, changedSinceMilestone: false }
 }
 
 /** 表明工作做到一半的硬信号，没有则返回 null。 */