-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Investigate 'Summary before compression' approach #23908
Copy link
Copy link
Open
Labels
area/agentIssues related to Core Agent, Tools, Memory, Sub-Agents, Hooks, Agent QualityIssues related to Core Agent, Tools, Memory, Sub-Agents, Hooks, Agent Qualitypriority/p0Critical and urgent (e.g., critical security vulnerability, major breakage).Critical and urgent (e.g., critical security vulnerability, major breakage).type/task🔒 maintainer only⛔ Do not contribute. Internal roadmap item.⛔ Do not contribute. Internal roadmap item.
Metadata
Metadata
Assignees
Labels
area/agentIssues related to Core Agent, Tools, Memory, Sub-Agents, Hooks, Agent QualityIssues related to Core Agent, Tools, Memory, Sub-Agents, Hooks, Agent Qualitypriority/p0Critical and urgent (e.g., critical security vulnerability, major breakage).Critical and urgent (e.g., critical security vulnerability, major breakage).type/task🔒 maintainer only⛔ Do not contribute. Internal roadmap item.⛔ Do not contribute. Internal roadmap item.
Type
Fields
Give feedbackNo fields configured for issues without a type.
What would you like to be added?
Confirm if we do, or do not have any opportunities around improving compression success (Previously mentioned by Joshua around “summary before compress” approach).
Why is this needed?
To improve the efficiency and success rate of chat history compression.
Additional context