Repository navigation
Releases
v0.3.0
What's Changed
Relay control commands
Send !status, !stop, !new or !help as the whole message (@bot !stop in mention-gated channels; /status etc. and the aliases !cancel / !reset also work). They are answered immediately, outside the per-channel run queue:
!status: what is running, for how long, how many messages are queued, and which conversation the channel resumes!stop: cancel the running agy task and drop queued messages (the in-chat fix for a stuck run)!new: forget the channel's resumed conversation (AGY_RESUME_BY_CHANNEL=true)
Messages that arrive while a channel is busy get a ⏳ reaction until their turn starts.
Inbound attachments
Files the user attaches are downloaded into the bridge inbox before the run. The inbox is added to agy's workspace (--add-dir) and the prompt lists each local path. Per-file failures are reported in the prompt, and inbox files older than 7 days are pruned. Opt out with AGY_DISCORD_RELAY_DOWNLOAD_ATTACHMENTS=false.
Process-tree kill
Cancel and timeout used to kill only the agy process. Tool commands it had started in their own session (setsid) survived as orphans. agy now runs as its own process group, and every descendant is collected from the process table before signalling (SIGTERM, then SIGKILL after 2s).
Safer restarts
Shutdown (SIGINT/SIGTERM/SIGHUP) cancels in-flight runs and leaves their messages pending. On restart, only pending messages younger than AGY_DISCORD_REPLAY_MAX_AGE_MS (default 1h, 0 = off) are replayed.
Fixes
queue.json/threads.jsonupdates are serialized per file; concurrent updates could silently drop a writemcpmode yields inbound handling to a live relay (no duplicate typing, ack reactions, pairing replies or queue writes);bridge_statusreportsrelay.running;download_attachmentreports per-file failures- Uses
Events.ClientReady(fixes the discord.jsreadydeprecation warning) doctorshows relay state, attachment download and replay settings- discord.js 14.28.1, @modelcontextprotocol/sdk 1.32.2
Full Changelog: v0.2.0...v0.3.0
v0.2.0
What's Changed
Per-channel relay outbox
Relay file delivery now uses one outbox subdirectory per Discord channel (<AGY_DISCORD_GENERATED_IMAGES_DIR>/<channel-id>/). Concurrent runs in different channels — or any other agy job writing to the shared base dir — can no longer get attached to the wrong reply. Detection also drops the 1s mtime slack (no more re-attaching the previous run's files on quick back-to-back messages), skips empty files, and attaches multi-file outputs oldest first. If attaching fails, the relay retries text-only so the answer itself is never lost.
Stuck-run hardening
A deadlocked agy --print that ignores SIGTERM is now SIGKILLed 2s after the timeout fires, instead of blocking the channel's serial queue forever. Exit signals are reported instead of code null.
Fixes (ported from codex-discord-mcp v0.2.0)
- MCP server now advertises the real package version instead of a hardcoded
0.1.0 - Hand-edited
access.jsonchannel entries missingallowUsersno longer crash the inbound gate - Long-message chunking no longer starts continuation chunks with a boundary space
doctorreports the deliverables dir; help output aligned
Full Changelog: v0.1.1...v0.2.0
agy-discord-mcp v0.1.1
Patch release that updates the published npm README install instructions and keeps GitHub Release publishing on npm trusted publishing.
agy-discord-mcp v0.1.0
Initial npm release of agy-discord-mcp.\n\nThis release publishes the Discord bridge and MCP tools for the agy (Antigravity) CLI.