Skip to content

Ensure saved checkpoints are flexible enough to support long term sessions #21920

@joshualitt

Description

@joshualitt

Today, the existing history checkpoints don't capture compression events. We should move away from just storing raw generated content, to saving a higher-level format that supports compression in a lossless way.

This will help stop the bleeding, but very large threads could still become unwieldy. As part of this work, we should come up with a medium term task to fix checkpoints once and for all, i.e. switch to a DB backed solution for history, or consider using multiple JSON files per checkpoint so we can optimize the save / resume accordingly.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/agentIssues related to Core Agent, Tools, Memory, Sub-Agents, Hooks, Agent Qualitypriority/p2Important but can be addressed in a future release.workstream-rollupLabel used to tag epics and features that are associated with one of the three primary workstreams🔒 maintainer only⛔ Do not contribute. Internal roadmap item.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions