local-webhook 0.8.1: stop recommending pinned subscriptions - #7
Merged
Conversation
The tool descriptions, the CLI usage text and the plugin README all told the agent to pin this box's own repos with ttl_hours:0 (and to pair renew_on_event with it). That is the one combination that reliably goes wrong: a delivery lands in whichever session happens to be active, so a pinned topic interrupts unrelated work indefinitely — no session "owns" a standing watch on a repo. Rewrite the guidance everywhere it appears to say the opposite: scope the TTL to the work in flight and let it lapse. The mechanism is unchanged — ttlHours:0 still pins, renewOnEvent still renews — only the advice moves. Pinning becomes reasonable once a subscription can ask for delivery into a fresh session instead of the active one (#1), since a cold run has no warm cache to lose; both the code comment and the README point there.
lionello
approved these changes
Jul 30, 2026
This was referenced Jul 30, 2026
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
2 participants
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.
The tool descriptions, the CLI usage text and the plugin README all told the agent to pin this box's own repos with
ttl_hours: 0(and to pairrenew_on_eventwith it). That is the one combination that reliably goes wrong: a delivery lands in whichever session happens to be active at the time, so a pinned topic interrupts unrelated work indefinitely — no session "owns" a standing watch on a repo.This rewrites the guidance everywhere it appears — the
INSTRUCTIONSblock, thettl_hoursandrenew_on_eventtool descriptions, the--ttlCLI usage, the expiry comment block inwebhook.py, and the plugin README (including the example filter entry, which used a pinned own-repo as its illustration).No behaviour change.
ttlHours: 0still pins andrenewOnEventstill renews; only the advice moves. Patch bump to 0.8.1 because the shipped tool descriptions are part of the plugin surface.Pinning becomes reasonable once a subscription can request delivery into a fresh session instead of the active one — sketched in #1 — since a cold run has no warm cache to lose. Both the code comment and the README point there rather than leaving the reader with a flat prohibition.
🤖 Generated with Claude Code
https://claude.ai/code/session_01PsqGhkpjsb4kKAdVz25xKN