Repository navigation
v1.6.1
1.6.1 - 2026-10-25
This release fixes agmsgd notices that could stop and never resume. If you turned agmsgd on in 1.6.0, update; nothing else is needed, and agmsgd restarts on the new code by itself. If agmsgd is off, it stays off, and the recommended setting is unchanged: agmsgd, chosen with /agmsg delivery.
Fixed
- agmsgd treats a notice as delivered once it is sent: a successful
codex queuecall for Codex, or a successful socket write for Claude Code. It no longer reads either tool's internal session files to confirm the notice was seen, and no longer withholds later notices while such a check is unanswered. The next notice goes out when new unread messages arrive; a failed send records its reason inagmsg daemon statusand is retried (#1743, #1744) - One stuck check can no longer stop agmsgd notices for every session. Each poll, channel and session has a time limit; work that exceeds it is abandoned with its reason shown in status, and the poll moves on.
agmsg daemon stopand SIGTERM finish even while a poll is stuck (#1754, #1762) - agmsgd.log records delivery events (notices sent, failures, expired attempts, session state changes and overrun polls), never message bodies, and is size-bounded (#1755, #1762)
- Windows: Codex sessions keep receiving notices when the start time of the
codex queuechild process cannot be read, for example when PowerShell is blocked orpwshis not installed (#1731, #1734) - Install, update and uninstall write to the Codex profile selected by
CODEX_HOMEinstead of always~/.codex/config.toml, and use nativeC:/paths on Windows (#1718, #1738) - A closed Claude Code session is no longer reported as addressable;
agmsg daemon status --alllists sessions that cannot be reached (#1732, #1737) actassays why a Claude Code session stayed on the Monitor instead of agmsgd (#1733, #1740)inboxandhistoryrefuse an unknown team instead of reporting an empty inbox (#1714, #1739)- herdr: existing agent names are kept when a pane is named (#1676)