fix(cli): prune tool outputs for large requests#10143
Conversation
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Resolved IssuesBoth warnings from the initial review were addressed in the latest commits:
Files Reviewed (3 files)
Reviewed by claude-sonnet-4.6 · 255,182 tokens |
|
@kilocode-bot is this ready to be merged? |
|
To use Kilo from GitHub you first need to link your GitHub account to Kilo. Link your Kilo account to continue. After linking, mention me again in this issue or pull request. |
|
@kilocode-bot is this ready to be merged? |
|
Based on the existing code review already completed on this PR, yes, it looks ready to merge! 🟢 The automated review gave it:
Both warnings from the initial review were resolved in subsequent commits:
All 3 files were reviewed with no outstanding issues. The change looks solid — it compacts older tool outputs at payload-limit boundaries while keeping normal-turn pruning opt-in for cache stability. |
* fix(cli): prune tool outputs for large requests * chore(cli): annotate pruning changes * fix(cli): preserve transforms after payload pruning
Compacts older tool outputs when a model request has already grown large, reducing long-session request payloads without restoring default pruning after every normal turn.
Keeps normal-turn pruning opt-in for cache stability, while pruning after compaction and at payload-limit boundaries where the prompt prefix is already changing or too large to send efficiently.