opencode-acp 1.14.15 → 1.14.16

package/README.md

@@ -492,6 +492,16 @@ For the complete list with root cause analysis, see the [bug tracker](https://gi
 
 ## Changelog
 
+### v1.14.16 — Raise context limits to 80%
+
+**Problem**: The compression thresholds were `maxContextLimit: 55%` / `minContextLimit: 45%`. The strong "over-limit" nudge fired as soon as context exceeded 55% of the model window. Combined with the fixed 50K growth threshold (v1.14.15), this still engaged compression relatively early, leaving usable context unused.
+
+**Fix**: Raise **both** `compress.maxContextLimit` (`"55%"` → `"80%"`) and `compress.minContextLimit` (`"45%"` → `"80%"`) in `lib/config.ts`. Compression now waits until context exceeds 80% before firing the strong "over-limit" nudge. Setting `minContextLimit` equal to `maxContextLimit` removes the legacy 45% early-engagement band entirely — `minContextLimit` only affects the nudge tip *tone* (`tipsVariant`), never whether a nudge fires; the actual nudge decision is `growthSinceLastNudge >= nudgeGrowthTokens || overMaxLimit`, so aligning both at 80% makes behavior uniform and drops the meaningless early tip tone. The `emergencyThresholdPercent: "98%"` backstop is unchanged. Users can override via `compress.maxContextLimit` / `compress.minContextLimit` in their config.
+
+Files: `lib/config.ts`. Tests: 976 pass.
+
+**Install**: `opencode plugin opencode-acp@latest --global`
+
 ### v1.14.15 — Pin nudge growth to fixed 50,000 tokens
 
 **Problem**: The T2/T3 nudge growth threshold was computed as 5% of the model context window (clamped 20K–50K via `resolveAdaptiveNudgeGrowth` from `context-compress-algorithms`). For sub-1M-context models this produced smaller thresholds (e.g. 10K at 200K, 20K at 400K), causing nudges to fire too eagerly and over-compress.

package/README.zh-CN.md

@@ -446,6 +446,16 @@ ACP 是 DCP 的直接替代品。迁移步骤：
 
 ## 更新日志
 
+ ### v1.14.16 — 将上下文 limit 提升至 80%
+
+**问题**：压缩阈值原为 `maxContextLimit: 55%` / `minContextLimit: 45%`。上下文一旦超过模型窗口的 55% 就会触发强「超限」nudge。配合 v1.14.15 固定的 50K 增长阈值，压缩仍较早介入，可用上下文未被充分利用。
+
+**修复**：将 `compress.maxContextLimit`（`"55%"` → `"80%"`）和 `compress.minContextLimit`（`"45%"` → `"80%"`）**同时**提升至 80%（`lib/config.ts`）。压缩现在等到上下文超过 80% 才触发强「超限」nudge。把 `minContextLimit` 设为与 `maxContextLimit` 相同，彻底移除旧的 45% 提前介入区间 —— `minContextLimit` 只影响 nudge 提示语气（`tipsVariant`），不决定是否触发；实际 nudge 判定为 `growthSinceLastNudge >= nudgeGrowthTokens || overMaxLimit`，两者都设 80% 使行为统一，并去掉无意义的早期提示语气。`emergencyThresholdPercent: "98%"` 兜底不变。用户可通过配置中的 `compress.maxContextLimit` / `compress.minContextLimit` 覆盖。
+
+文件：`lib/config.ts`。测试：976 通过。
+
+**安装**：`opencode plugin opencode-acp@latest --global`
+
  ### v1.14.15 — 固定 nudge 增长阈值为 50,000 tokens
 
 **问题**：T2/T3 nudge 增长阈值按模型上下文窗口的 5% 计算（通过 `context-compress-algorithms` 的 `resolveAdaptiveNudgeGrowth` 钳制在 20K–50K）。对于低于 1M 上下文的模型，这会产生更小的阈值（例如 200K 时为 10K，400K 时为 20K），导致 nudge 触发过于频繁、过度压缩。

package/dist/index.js

@@ -1484,8 +1484,8 @@ var defaultConfig = {
     permission: "allow",
     showCompression: true,
     summaryBuffer: true,
-    maxContextLimit: "55%",
-    minContextLimit: "45%",
+    maxContextLimit: "80%",
+    minContextLimit: "80%",
     nudgeFrequency: 5,
     minNudgeContextPercent: 15,
     iterationNudgeThreshold: 15,
@@ -8949,7 +8949,7 @@ import { writeFile as writeFile2, mkdir as mkdir2 } from "fs/promises";
 import { join as join3 } from "path";
 import { existsSync as existsSync3 } from "fs";
 import { homedir as homedir3 } from "os";
-var LOG_VERSION = true ? "1.14.15" : "dev";
+var LOG_VERSION = true ? "1.14.16" : "dev";
 var Logger = class {
   logDir;
   enabled;