Skip to content

RewindStore TTL should be configurable per content type #13

@baridevish

Description

@baridevish

We're using claw-compactor in a long-running agent workflow where some compressed content needs to stay retrievable for hours while other content (like intermediate search results) can expire quickly.

Currently the TTL is global (default 600s). It would help if different stages could set different expiry times — for example, Ionizer results might need 1 hour while SearchCrunch results only need 5 minutes.

One approach: let each stage pass a ttl hint when calling rewind_store.store().

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions