abc/analysis_claude_code
1
0
Fork 0
mirror of https://github.com/shareAI-lab/analysis_claude_code.git synced 2026-09-22 05:13:48 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs(s08): clarify reactive_compact aggressive wording refers to trigger, not compression

Browse Source 
The original phrasing "more aggressive than compact_history" was
ambiguous: the code shows reactive_compact is actually more
conservative in compression (keeps ~5 recent messages vs replacing
everything with a summary).  The real difference is the trigger
mechanism — reactive_compact is an emergency response to a 413
error, not a proactive threshold-based trigger.

Clarify in all three README languages that the aggressiveness is
about the trigger, not the compression strategy.

Closes #467
This commit is contained in:
root
2026-07-28 22:17:25 +08:00
parent 581241cdc7
commit b6eb5c0f3b
3 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
s08_context_compact/README.md
View File

@@ -136,7 +136,7 @@ def compact_history(messages):
有时候 API 还是返回 `prompt_too_long`（413），上下文增长速度快于压缩触发速度时。
这时触发 **reactive_compact**：比 compact_history 更激进，从尾部回退，但仍要避免留下孤立 `tool_result`。
这时触发 **reactive_compact**：触发方式比 compact_history 更激进（API 报错后的应急手段），但压缩策略更温和，保留最近约 5 条原始消息，只总结较早历史。同样避免留下孤立 `tool_result`。
```python
def reactive_compact(messages):