Skip to content

fix(session_start): point an installed hook at plumb hooks, not at installing it - #548

Open
atlas-from-plumb wants to merge 1 commit into
mainfrom
atlas/stamp-notice-remedy
Open

atlas-from-plumb wants to merge 1 commit into
mainfrom
atlas/stamp-notice-remedy

Conversation

@atlas-from-plumb

Copy link
Copy Markdown
Collaborator

Why

Found by dogfooding plumb from a Claude desktop Code-tab session running a daemon built before #531. The hook was installed and stamping, but the daemon didn't advertise plumb_agent, so the connector stripped the stamp. session_start's notice then said only "plumb hooks install claude-code stamps every call", which sent the caller in a circle to install something it already had.

Change

Both no-identity notices (refused and dormant) in internal/tools/session_start_stamp.go now add that plumb hooks says why the call was not stamped. #536 made plumb hooks status report a daemon that doesn't list plumb_agent, so that command gives the real reason.

Tests

TestStampChannelNotices_PointAnInstalledHookAtItsDiagnosis pins both notices. The brief-packet byte budget still passes. GOWORK=off go test ./... -count=1 and -tags=integration ./internal/cli/: ok. The CHANGELOG entry is under 0.20.4 (unreleased), and the placement check passes.

🤖 Generated with Claude Code

…installing it

When a call arrived without a per-call identity, session_start's notices
said only "`plumb hooks install claude-code` stamps every call". With the
hook already installed, the usual cause is a daemon too old to accept the
key Claude desktop's connector passes through (found by dogfooding on a
pre-#531 build). The advice sent the caller round in a circle. Both
notices now add that `plumb hooks` says why the call was not stamped.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Plumb-Session: scarlet-viper

This branch has not been deployed

No deployments
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