Add Telegram notifications plugin (noobitoo.telegram-notifications) - #4
Open
NooBiToo wants to merge 3 commits into
Open
Add Telegram notifications plugin (noobitoo.telegram-notifications)#4NooBiToo wants to merge 3 commits into
NooBiToo wants to merge 3 commits into
Conversation
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.
Adds a community notifications plugin to the marketplace index.
Plugin
noobitoo.telegram-notificationsv0.4.1["notifications"](community; noofficial)>=1.4.0, pluginApi 1What it does
Sends a Telegram message when an agent changes status (finished, needs attention, stuck, error, waiting — user-configured keyword filter, optional workspace filter, anti-spam quiet window persisted across worker restarts).
main.mjs, plain Node) subscribes toagent.status.changedand posts via the Telegram Bot API. Messages use human titles per status (✅ finished / 🙋 needs attention /{{title}} {{worktree}} {{state}} {{time}}placeholders.~/.orca-plugin-config/telegram-notifications.json) so user edits never trip the host's content-hash integrity check.storage,secrets,settings:own,events:subscribe,notifications:show— no terminal, no workspace access.Validation
parsePluginManifestschema rules andparsePluginLanguagePackArtifactdiscipline applied to config handling); install from git URL with#refverified end-to-end on Orca 1.4.191/1.4.192 (Windows): install → review → enable → command palette → settings page → Telegram delivery.node scripts/test-local.mjs).What's new in v0.4.1
profiles/<profile>/orca-data.json): project line + workspace title (git worktrees use their OrcadisplayName, folder workspaces their name, e.g.gittracker / #GT-89); falls back to the path basename if the store is unavailable.What's new in v0.4.0
worktreeId) instead of the rawuuid::path, localized status words, the noisy pane line removed.Stophook, persisted by the host inagent-hooks/last-status.json) is appended to the notification (💬, truncated to 700 chars) — the plugin worker reads it directly from disk since the plugin event payload strips this field. Degrades gracefully: no file/field → no 💬 line.Note
This is the second plugin from the same author as #3 (Russian language pack); PRs are independent and can be reviewed/merged separately.