Unverified50% confidenceSolutionExact time
Appending retention instructions after the /compact command (such as "compact but keep the API decisions and database schema") can guide the summary to retain important information.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/21/2026
First Seen
Valid until: 1/19/2027
Sources
Related Entities
Related Claims
UnverifiedThe /compact command works by summarizing and compressing the current session, retaining key decisions and code change records while discarding redundant intermediate discussions.72% similarVerifiedThe general principle for achieving cache hits is to keep the prefix of the request context as stable as possible, placing fixed content such as system prompts and tool definitions at the very front, with per-turn user input appended at the end.70% similarVerifiedCommon context pruning strategies include sliding window (retaining the most recent N messages), summary compression (summarizing old messages into a summary), and importance filtering (prioritizing the retention of tool call results).68% similarVerifiedTo maximize cache hit rate, stable content (system prompts, file contents) should be placed at the prefix of the prompt, with dynamic content appended at the end67% similarUnverifiedContext engineering is essentially information scheduling within a limited window: deciding what to keep, what to compress, and what to move out of the window and recall on demand from external storage (such as a vector database).67% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1079620API
curl https://kongchang.com/api/v1/knowledge/claims/1079620MCP
get_claim(id=1079620)