opencode-acp 1.3.0 → 1.3.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.js
CHANGED
|
@@ -6493,6 +6493,8 @@ Compression replaces raw conversation content with dense summaries. When used co
|
|
|
6493
6493
|
|
|
6494
6494
|
The key principle: compress based on context pressure, not habit. When context is ample, compress rarely or not at all. When context is tight, compress aggressively but selectively. The runtime context usage indicator tells you the current pressure level.
|
|
6495
6495
|
|
|
6496
|
+
Target the largest UNCOMPRESSED content first. Savings scale with original size \u2014 compressing a 5000-token tool output frees far more than re-shrinking an already-summarized 300-token block.
|
|
6497
|
+
|
|
6496
6498
|
CONTEXT PRESSURE LEVELS
|
|
6497
6499
|
|
|
6498
6500
|
- Ample: Context is well below the threshold. Do NOT compress unless there is obvious waste (huge terminal dumps, duplicated content). Focus entirely on your task.
|
|
@@ -6501,11 +6503,21 @@ CONTEXT PRESSURE LEVELS
|
|
|
6501
6503
|
|
|
6502
6504
|
WHAT TO COMPRESS FIRST (high value, low risk)
|
|
6503
6505
|
|
|
6504
|
-
-
|
|
6505
|
-
-
|
|
6506
|
-
-
|
|
6507
|
-
-
|
|
6508
|
-
-
|
|
6506
|
+
- Agent/subagent review and consultation results: Prime compression targets when context pressure rises \u2014 the surrounding reasoning and tool-call chatter is typically the largest block of uncompressed content. Note: if the agent tool is in your protected list, its output is auto-preserved in the summary, so the savings come from the surrounding conversation, not the agent output itself. Compress once you have fully consumed the results (all recommended actions applied or recorded in files). Recover via \`decompress\` while the block is still active. Re-invoking the agent is a last resort \u2014 it is a fresh run, not a cache hit.
|
|
6507
|
+
- Verbose command output (build/test runs, git diff/log/status, publish logs, directory listings): Once you have read the result, compress. Keep only the verdict \u2014 pass/fail status, commit hash, version number, or count. For failures, keep the specific error messages and file/line references needed to act on them. The full output is reproducible by re-running the command.
|
|
6508
|
+
- Exploration that led nowhere (failed approaches, dead-end searches): Compress to a one-line note about what was tried and why it failed.
|
|
6509
|
+
- Redundant tool results (reading the same file multiple times, repeated status checks, exhausted search results): Keep only the most recent result.
|
|
6510
|
+
- Intermediate steps of completed multi-step tasks: Once the task is done, compress the process. Keep only the final outcome.
|
|
6511
|
+
- Resolved discussion threads (clarification rounds, negotiated requirements, design debate that reached a decision): Once a conclusion is recorded, compress the back-and-forth. Keep the decision and its rationale.
|
|
6512
|
+
- Large file contents that have already been used and are no longer needed: Compress to a summary of key functions, types, or patterns.
|
|
6513
|
+
|
|
6514
|
+
DO NOT RE-COMPRESS (low value, diminishing returns)
|
|
6515
|
+
|
|
6516
|
+
- Already-compressed block summaries: Re-compressing a summary into a shorter summary saves negligible tokens. If a block needs better detail, use \`decompress\` to restore it, then compress the original content properly. Exception: if a block-aging warning flags specific block IDs as facing GC truncation, re-summarize exactly those flagged blocks into a fresh range \u2014 this preserves detail that GC would otherwise destroy.
|
|
6517
|
+
- Short messages (1-3 sentences): The compression overhead (block metadata, summary structure) may exceed the tokens saved.
|
|
6518
|
+
- Content whose immediate use is complete \u2014 the task it supported is done and no open todo/plan references it. If still in active use, let it stay.
|
|
6519
|
+
- User instructions and requirements: These must remain visible until the task is complete.
|
|
6520
|
+
- Tool calls that are still pending or in-progress: Wait until the result is returned and consumed.
|
|
6509
6521
|
|
|
6510
6522
|
WHAT TO COMPRESS CAREFULLY (high risk - verify before compressing)
|
|
6511
6523
|
|