fix: update message uses 'agend start' + skip empty bot messages in collab log#73
Open
changhansung wants to merge 262 commits into
Open
fix: update message uses 'agend start' + skip empty bot messages in collab log#73changhansung wants to merge 262 commits into
changhansung wants to merge 262 commits into
Conversation
… dead panes and respawn
…ownload - Discord adapter: MIME-based attachment kind detection (photo/video/audio/document) - Discord adapter: attachmentUrls Map with 1000 cap, fetch-to-file downloadAttachment - Classic mode: processAttachments in handleClassicChannelMessage with extraMeta passthrough
- Discord adapter: fetch referenced message content via fetchReference() - Classic mode: pass replyToText through IPC meta as reply_to_text
…all users Discord adapter now emits all messages. Fleet-manager checks access: - Classic channels: all users allowed (for chat logging) - Topic/general: only allowed_users pass
- Remove guildId filter from messageCreate — messages from any server pass through - Fleet-manager access control + routing handles which channels are valid - Fixes: messages from non-primary server were silently dropped
- Restore .kiro/settings/mcp.json to .gitignore (machine-specific) - Remove ~/Projects/ from .gitignore (local path) - Remove plugin package-lock.json (managed by root workspaces)
… stale drop - Reduce waitForIdle timeout to 10s for lightweight (classic) instances - Add queue depth counter with warning at depth > 3 - Drop stale user messages (>60s in queue), preserve cross-instance messages
- Apply sanitizeInstanceName in ClassicChannelManager.load() to match handleClassicStart registration path, preventing workspace directory drift after rebase/restart - Allow bare attachments (images without /chat prefix) to be forwarded to classic channel agents - Include attachment info in classic channel chat logs
restartInstances() killed classic tmux windows during orphan cleanup but never restarted them. Only reregisterClassicChannels() was called (routing only). Add the same startup logic from startAll() to restart classic instances with concurrency 3.
capture-pane leaks 'can't find window' to stderr when instances are still starting up. Pipe stderr to suppress.
…bare attachments - Bare image (no /chat): download to ~/.agend/workspaces/<instance>/inbox/, log path in chat-log, react 📸, don't forward to agent - /chat + image: download to workspace inbox, forward to agent with correct workspace path in image_path and text - Topic mode image handling unchanged (still uses processAttachments directly)
Strip photo from attachments before processAttachments when already saved to workspace inbox, preventing orphan file in daemon inbox.
P0: Discord adapter security hardening - messageCreate: reject messages from other guilds - interactionCreate: reject interactions from other guilds P1: setup-wizard Discord channel type support - Add channel type selection step (Telegram / Discord) - Discord flow: token verification, guild selection, user ID input - buildFleetConfig generates correct Discord config (type: discord, bot_token_env: AGEND_DISCORD_TOKEN, guild_id) - WizardAnswers extended with channelType and guildId fields - Telegram flow unchanged
Adds optional general_channel_id prompt after User ID step. Written to fleet.yaml under channel.options when provided.
After Discord flow completion, both setup-wizard and quickstart now display: 'Classic Bot Mode: Use /start in any Discord channel to start an agent. Use /chat to talk.'
…ugh guildId check messageCreate, interactionCreate, and channelDelete handlers now check openChannels set before rejecting messages from non-primary guilds. This allows classic bot channels registered across multiple servers to continue functioning while still blocking unregistered channels. Added debug logging for non-primary guild classic channel events.
…dcoded 1 Telegram General Topic has thread_id=1 by convention, but Discord channels have snowflake IDs. When general_channel_id is set in fleet.yaml options, use it as the general instance's topic_id. Fixes 'Unknown Channel' error on fleet start with Discord.
- ClassicBotYaml.defaults gains allowed_guilds?: string[] - isGuildAllowed(): empty/unset list allows all guilds (backward compat) - Discord adapter slash_command events now include guildId - handleClassicStart checks guild whitelist before registering channel
After fleet.yaml is written, Discord quickstart now asks: - Set up ClassicBot? (allows /start in any channel) [Y/n] - If yes: collects allowed_guilds (primary guild pre-filled, can add more) - Asks default backend (defaults to fleet backend) - Writes ~/.agend/classicBot.yaml matching ClassicBotYaml interface
resolveReplyThreadId returns undefined for classic instances (not in fleetConfig.instances). Add fallback to classicChannels.getChannelIdByInstance() so reply/react/edit tools work correctly for classic bot channels.
Format: [user:name via platform, id:USER_ID] message Enables classic agents to @mention users in replies.
Teaches all instances how to @mention users and bots using the id: field from inbound messages.
In topic mode, daemon should not block reply when lastChatId is unset. Fleet-manager has the classicBot channelId fallback to route correctly.
allowed_guilds: {} (object instead of array) caused all groups to be
rejected. Now uses Array.isArray check — non-array values treated as
'allow all'.
/stop@other_bot was being stripped to /stop and executed by all bots in the group. Now checks if the @suffix matches our bot username — if not, ignores the command entirely.
…fore start() Two bugs: 1. Primary adapter's 'started' handler never set world.botUsername (only secondary adapter did). This caused isBotMentioned to always be false for TG classic mode on the primary adapter. 2. adapter.start() was called BEFORE event listeners were attached, so if 'started' fired synchronously it would be missed. Fix: set botUsername in primary handler + move start() after all event registrations.
- /start in groups: requires admin after isGroupAllowed passes - /stop: requires admin - /raw via @mention: requires admin - Regular @mention conversation remains open to all users
- systemd: Restart=on-failure + RestartSec=5 (auto-restart on crash) - launchd: already has KeepAlive=true (no change needed) - Startup priority: general_topic instances start first and wait, then remaining instances start with staggered concurrency - Both initial start and restart paths use same priority logic - General instance failures logged but don't block other startups
TG: /status, /restart, /sysinfo → [Fleet] TG: /start, /stop, /chat → [ClassicBot] DC: all slash commands → [ClassicBot]
1. Daily update check: fleet daemon checks npm for new versions every 24h (first check after 1h). Notifies general topic if update available. Beta instances also check @beta tag. 2. /update detached restart: after npm install, spawns a detached shell that sleeps 2s then restarts the service. Prevents the restart from killing the update response. 3. agend doctor expansion: adds fleet-level checks for fleet.yaml syntax, port 19280 availability, stale MCP sockets, service ExecStart mismatch, kiro-cli auth, and working_directory existence.
feat: daily update check, /update detached restart, doctor expansion
feat: doctor checks for service Restart policy and daemon-reload
1. sd-notify: READY=1 after generals start, WATCHDOG=1 every 30s, STOPPING=1 on shutdown. Zero dependencies (uses net.createConnection). 2. systemd template: Type=notify, NotifyAccess=main, WatchdogSec=60. systemd kills+restarts fleet if no watchdog ping for 60s. 3. General instance startup failure now sends notification to the general topic channel with error details.
feat: systemd watchdog + general startup failure notification
…ollab log - Replace all user-facing 'agend fleet start' with 'agend start' - Collab mode: skip logging empty bot messages (no text, no attachments)
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.
Closes #6 and #7
agend fleet startmessages changed toagend start