Proactively offer push notifications to existing GMs (plugin 1.4.0) - #36
Merged
Conversation
…4.0) Existing GMs had no way to discover the task-event channel — they'd only get it if the user happened to run /gm-doctor. Ship a plugin SessionStart hook so the GM itself raises it. - hooks/hooks.json + hooks/channel-nudge.sh: a SessionStart hook (delivered by the plugin, so it reaches GMs that already exist once they update). It is scoped to taskyou-os GM dirs and self-disabling — it injects an additionalContext note only when the channel ISN'T deployed, prompting the GM to offer '/gm-doctor' to the user. Silent otherwise. - plugin.json: register hooks + bump 1.3.0 -> 1.4.0; marketplace.json synced. - README: document enabling marketplace auto-update (off by default for third-party) and the proactive offer. - qa harness: assert the nudge fires on a channel-less GM and stays silent on a channel-equipped GM / outside GM dirs. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Summary
Follow-up to #35. Publishing the channel made it available, but existing GMs still had no way to discover it — they'd only get push notifications if the user happened to run
/gm-doctor. This makes the GM raise it itself.How
A plugin-shipped
SessionStarthook — which reaches GMs that already exist the moment they update the plugin (a nudge baked into rendered GM files can't do that). It's:config.env+bin/ty-remote).additionalContextnote only when the channel isn't deployed; silent once it is, and silent in non-GM dirs.When it fires, the GM reads the note and offers the user, in natural language: "Push notifications are available — want me to run
/gm-doctorto enable them?" One yes and it's done.Changes
hooks/hooks.json+hooks/channel-nudge.sh— the SessionStart hook (top-levelhooks/, distinct fromtemplates/hooks/which are the ty server hooks).plugin.json— register"hooks", bump1.3.0 → 1.4.0;marketplace.jsonsynced.README— document enabling marketplace auto-update (off by default for third-party) + the proactive offer.qa/harness — asserts the nudge fires on a channel-less GM and stays silent on a channel-equipped GM / outside GM dirs. 29/29.The full organic chain this completes
enable auto-update (one-time) → CC pulls the new plugin → next GM launch, the GM offers to enable push notifications → one yes → /gm-doctor deploys it → restart.🤖 Generated with Claude Code