fix: Discord thread replies, Telegram thread support, and queue reliability#142
Open
geoffwellman wants to merge 5 commits intoTinyAGI:mainfrom
Open
fix: Discord thread replies, Telegram thread support, and queue reliability#142geoffwellman wants to merge 5 commits intoTinyAGI:mainfrom
geoffwellman wants to merge 5 commits intoTinyAGI:mainfrom
Conversation
…bility Discord: - Respond to all messages without requiring @mention - Create threads for responses in server channels - Typing indicator targets the thread Telegram: - Respond in groups/supergroups (not just private chats and forums) - File attachments sent to the correct forum topic thread - Typing indicator targets the correct thread - Commands (agent, team, reset, pairing) work in threads Queue reliability: - Fix claude not found in PATH by adding ~/.local/bin to spawn env - Add 5-minute timeout to agent commands to prevent hung processes - Process pending messages on startup (not just on new events) - Add 30-second fallback poll so queue never gets stuck Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Add ChannelRouting and ChannelConfig types to Settings - Add resolveChannelAgent() for channel name → agent mapping - Add parseMentionRouting() for @agent extraction from messages - Discord: channel routing from settings, @mention priority routing, default_agent fallback for guild messages - Telegram: @mention routing in groups/supergroups, topic/group name routing via channel_routing config, default_agent fallback - Existing channel_routing in settings.json now functional Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Add `timeout` field to AgentConfig (seconds, default 300) - Add RunCommandOptions with onOutput callback for stdout streaming - invokeAgent accepts InvokeOptions to forward onOutput to runCommand - Queue processor sends periodic progress updates to chat every 60s for agents with timeout > 5min, so users know the agent is still working - Progress messages include elapsed time and last output snippet Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Threads have their own name (the thread title), not the parent channel name. Now resolves message.channel.parent.name when in a thread so channel_routing maps correctly. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This was referenced Feb 28, 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.
Summary
Changes
Discord ()
Telegram ()
Queue processor ()
Agent invocation ()
Test plan
🤖 Generated with Claude Code