Skip to content

fix(docgen): content-hash dedup — stop re-injecting identical READMEs in one session - #10

Merged
decider merged 1 commit into
mainfrom
fix/content-hash-dedup
May 25, 2026
Merged

fix(docgen): content-hash dedup — stop re-injecting identical READMEs in one session#10
decider merged 1 commit into
mainfrom
fix/content-hash-dedup

Conversation

@decider

@decider decider commented May 25, 2026

Copy link
Copy Markdown
Owner

Session dedup keyed on absolute README path → byte-identical READMEs at different paths (sibling worktrees of the same repo) were injected 2–3× per session. Per the Claude Code docs, hook additionalContext is not prompt-cached — appended as a system-reminder every turn — so every avoided re-injection saves real bytes.

Switch dedup to sha1(README full text). End-to-end on the canonical repo: two worktrees of main, same deep file once in each. Before: 8,741 chars each. After: 8,741 then 0. Suite green.

🤖 Generated with Claude Code

Session dedup keyed on absolute README path → identical content at
multiple paths (sibling worktrees) was injected 2-3× per session.
Switch to sha1(README full text). Hook additionalContext is NOT
prompt-cached, so every avoided re-injection saves real bytes per turn.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
@decider
decider merged commit f7de10f into main May 25, 2026
@decider
decider deleted the fix/content-hash-dedup branch May 25, 2026 05:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant