Repository navigation
feat(hooks): let the primer be disabled on its own - #23
Merged
Merged
Conversation
The primer is fixed cost paid on every session, and nothing here has ever measured what it buys. Deleting it because another project deleted theirs would be a guess; keeping it because it feels useful is the same guess wearing the other hat. CD_PRIMER=0 makes the question answerable by changing that one variable. Counting and guide seeding run before the opt-out, so switching the primer off leaves every other side effect intact and keeps an A/B honest. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
chipfighter
changed the base branch from
feat/skill-portability-and-safety
to
main
August 2, 2026 09:45
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.
Stacked on #22. Review that one first; this branch adds a single commit.
Why
The SessionStart primer is 1301 of the 4580-character fixed context budget —
28% — and nothing here has ever measured what it buys. Deleting it because
another project deleted theirs would be a guess. Keeping it because it feels
useful is the same guess wearing the other hat.
CD_PRIMER=0makes the questionanswerable by changing that one variable.
Counting and guide seeding run before the opt-out, so switching the primer off
leaves every other side effect intact and keeps an A/B honest.
Version
Part of v0.9.0. The owner pulled it into the frozen scope and the v0.9.0 entry in
the project guide was amended to name it. Both manifests already read 0.9.0, so
this branch needs no further version change — merge it into #22 and ship the two
together.
Verification
Written test-first: the new case failed because the behavior did not exist, not
from a typo, then passed on an eight-line implementation. All four suites green.
Note for whoever runs the A/B:
claude -pexecutes the installed plugin fromthe plugin cache, not the working tree. An earlier attempt scored a
CD_PRIMER=0run as primer-off while the installed copy was 0.8.1, which has no such flag —
both conditions were primer-on and nothing was measured. Install the build that
contains the flag, then confirm
EXTREMELY_IMPORTANTis absent from a livestream before trusting any number.
🤖 Generated with Claude Code