How to use dsh-compaction-tool-result-pruner

This article is derived from the plugin's already-indexed fields (wiki / faq / compatibility_json / readme), not freshly generated by AI. Source field is noted at the end of each section.

Quick start

Replay-safe model-free head/middle/tail pruning for tool-result surface nodes

— source: plugins.ai_summary

Install & verify

dsh plugin --profile web add npm:@deepseek-ai/dsh-compaction-tool-result-pruner

Run the command above in your DSH Web Profile. Then enable the plugin in the plugin list.

— source: plugins.install

Key points

• Character budgets are not token budgets — provider token density varies, so ctx.tokenMeter remains the authority for deciding whether pruning relieved request pressure.
• Pruning is syntactic — it retains the beginning and end without interpreting which middle lines are semantically important.
• Grapheme clusters can split — code-point slicing protects surrogate pairs but does not perform locale-aware grapheme segmentation.

— source: plugin_wiki.readme_en (fallback readme_raw)

Pitfalls

Review the upstream repo before installing. This guide is auto-derived from indexed fields and may lag the latest release. If anything contradicts the official docs, treat the upstream source as authoritative.

— source: general rule