Repository navigation
feat: notification channels per Bot and per kind - #49
Merged
Merged
Conversation
Feed notes now carry channel and member. A Bot's note goes to its own channel bot_<slug>, named after the Bot (renamed in place, never deleted), in a Bots group. system.agent goes to News and agents, system.monitor to Watches, chat.* to Chat updates, the rest to Dashboard alerts (the old channel id), all in a Kiro Crew group. Importance stays HIGH. Each channel has its own stack and summary. The Settings row is now Notification types.
rayvader
enabled auto-merge
November 7, 2026 15:18
cmd notification list_channels exits non-zero on the CI emulator, which ended the feature with no message. dumpsys alone lists the channels.
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
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
Notification channels per Bot and per kind (Raymond's option C, "both"), so sound and mute can be set per channel in Android settings.
memberbot_<slug>, named aftermember.namesystem.agentnews"News and agents"system.monitorwatches"Watches"chat.*/session.*chat"Chat updates"alerts"Dashboard alerts" (old id)Alertparseschannelandmember {slug, name}; older feeds without them still work (fallbackalerts).trip-helperbecomes "Trip Helper".NotificationChannelGroup. Existing channels get the Kiro Crew group (Android allows setting a group on a channel that has none). No channel is deleted; importance stays HIGH.alert.path. App updates and the Instant alerts channel are unchanged.ACTION_APP_NOTIFICATION_SETTINGSis renamed from "Sound and vibration" to "Notification types", so there is one row, not two.core/AlertChannels.Tests
AlertChannelsTest: member, agent, monitor, chat, unknown, missing fields, odd member shapes, naming frommember.name(slug-like, empty, long), rename keeps the id, safe slugs, feed parsing old and new.Instant alerts: a fake Bot note and an agent note; checksbot_e2e-demo-botis in groupbotsnamed "E2E Demo Bot",newsandalertsare inkirocrew, each note is on its channel, a rename updates the name in place, and the settings page shows the Bots group (screenshot).