Repository navigation
feat(agents): per-agent prompt-cache TTL pin, 1h for implement-next - #411
Merged
danielhanold merged 9 commits intoOct 11, 2026
Merged
danielhanold merged 9 commits into
danielhanold merged 9 commits into
Conversation
…visibility fold Review finding: isAgentPin hand-listed model/effort/runner, so a repository-layer agents.<harness>.<agent>.cache_ttl was carried into the private config instead of being dropped and reported. Derive the agent-pin leaves from the config registry's agents.* rows instead of a spelling list.
…sting Review finding: agentLines rendered only model / effort, so the shipped 1h cache TTL on claude implement-next, a global override, and a global auto that clears it were all invisible in the human effective block. Append a ttl segment when a pin resolves or a layer declared one, and name the cache_ttl layer in the bracket when it differs from the model's.
- AgentDigest digests cache_ttl only for harnesses in cacheTTLHarnesses, since the digest identifies what was rendered; add a test that a codex digest is unchanged by a cache_ttl. - defaults.go package comment anchors the agent table's parity oracle on testdata/repositories/v0.9.13 and its PROVENANCE.md entry. - agent-layer.md drops the dated per-agent cost table and figures, keeping the qualitative reason; regenerate embedded assets and lower the budget row to 212/1951.
danielhanold
deleted the
feat/per-agent-prompt-cache-ttl-pin-shipped-1h-for-implement-next
branch
October 11, 2026 14:48
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an optional per-agent
cache_ttlpin besidemodelandeffort. The Claude Code wrapper renders it asexperimental.cacheTtl, and docket ships1hfor the Claudedocket-implement-nextagent only, which loses about half its cost to prompt-cache expiry while it waits on builds and suites.cache_ttlblocks writes like any agent pin;cache_ttl: autoclears the shipped pin.agent-cache-ttl-droppedinstall warning (none with shipped defaults).docket diagnostic configshows the TTL; the private-visibility fold now recognises agent pins from the config registry.docs/install/models-and-effort.mdand the agent-layer reference.Review (docket-review-standard)
cache_ttlas an agent pincache_ttlinternal/config/defaults.go