Cairn

Configurable Anthropic prompt cache TTL setting

NousResearch/hermes-agent · cluster 3047 · agent

Data as of

Nothing open on GitHub. Fix merged in #15065. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 2 issues already closed.
Fix event
A fix was merged to main in PR #15065. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this partially resolved, deciding PR #15065. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and pull requests concern adding a configurable TTL option for Anthropic prompt caching, allowing users to choose between cache duration tiers (e.g., 5 minutes vs 1 hour) via configuration. The work spans feature requests and implementation attempts targeting config.yaml or similar settings.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #15065 feat: configurable prompt_caching.cache_ttl (5m default, 1h opt-in) — salvage #12659

    merged to main

    files: cli-config.yaml.example, hermes_cli/config.py, run_agent.py, scripts/release.py, tests/run_agent/test_run_agent.py, website/docs/developer-guide/context-compression-and-caching.md

2 PRs closed without merging

From the close comments: merged via another change 1 · superseded by another PR 1

  • #3082 feat(gateway): configurable prompt cache TTL via config.yaml · superseded by another PR → #15065, #12659
  • #12659 feat: configurable prompt_caching.cache_ttl for Anthropic TTL tier · merged via another change → #15065, #14812, #3082
Closed issues · 2
  • Closed#3047Feature: Configurable prompt cache TTL via config.yaml
  • Closed#14971Feature request: make prompt cache TTL configurable (5m vs 1h)
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.44: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
agent
Merged PRs
#15065
Closed issues
2
Attempts
2 PRs closed without merging
Fix link checked
24 Apr 2026. This confirmation is old and may be out of date (a revert or reopen would not have invalidated it here); re-verify.

For your agent

The same facts, typed.

cluster/3047.json
cluster/3047.md