Field noteOct 25, 20261 min read1 source

agmsg 1.6.1 fixes agmsgd notifications to Claude Code and Codex sessions that could stop permanently

In one minute

agmsg v1.6.1 has been released for the open-source messaging tool used to let CLI coding agents communicate as a team.

What changed: agmsg v1.6.1 adds a notification-reliability fix for agmsgd messages to Claude Code and Codex sessions.

The release fixes a failure in agmsgd, its resident notification service, where notices to Claude Code and Codex sessions could stop and never resume.

The new version considers a notice delivered after a successful Codex queue call or a successful socket write to Claude Code. It no longer reads the tools’ internal session files to verify that a notice was seen, and it no longer blocks later notices while that verification remains unanswered. Failed sends are recorded in daemon status and retried.

The release also adds time limits per poll, channel, and session, so a stuck check should not halt notices for every session. Its log now records delivery events without message bodies and is size-bounded. Windows fixes cover Codex queue child-process start-time lookup and use of the CODEX_HOME-selected profile.

The project tells users who enabled agmsgd in version 1.6.0 to update; the daemon restarts on the new code automatically. The release notes do not establish how many installations encountered the issue, whether messages were lost, or that delivery is guaranteed in every failure mode.

Evidence / sources

  1. 1github.com/fujibee/agmsg/releases/tag/v1.6.1
All Field Notes

Next reads

Read next

Open the graph
  1. 01topicCodexExplore the codex topic hub.
  2. 02topicClaudeExplore the claude topic hub.
  3. 03topicClaude CodeExplore the claude-code topic hub.
  4. 04archiveField NotesOpen the latest editorial analysis.
  5. 05source ledgerSource LedgerInspect the public source evidence graph.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract