Skip to content

v2.19.1

Choose a tag to compare

@github-actions github-actions released this 18 Oct 19:53
· 1008 commits to main since this release
ee92a5b

Release 2.19.1: what's on dev since 2.19.0.

  • Bots on a schedule no longer pile up processes (#143). A routine run's agent now stops as soon as the run ends when nothing else is using the bot, together with everything it started. A bot that only runs on a schedule is up only while a run works. When the bot is also in a conversation, only the run's session closes and the agent stays for what comes next. (On Windows, where agents are never stopped for idleness, the run's session closes instead.) Until now each run left its MCP servers running, and a Codex bot gained one more set per run. Opening a run's thread still resumes its session.
  • A chat whose agent session ended comes back: after an internal error the agent gave no reason for, the session is closed and loaded again on the next message, instead of every later message failing with "The Claude Agent session has ended". Failed turns now report their reason to usage analytics.
  • iPhone: no crash when the microphone is briefly unavailable during a voice call or dictation, or when the direct connection to the computer drops.
  • Desktop: no crash on a Mac without a microphone, and GPU fallbacks no longer show up as errors.

Known upstream issue: codex-acp titles each new session in an extra Codex thread it never closes, so a Codex bot that stays in use keeps one set of the user's Codex MCP servers per new session until it goes idle (agentclientprotocol/codex-acp#628, fix in review: #629).

No wire changes; no minApp change.

What's Changed

  • Codync 2.19.1: scheduled bots stop between runs, crash fixes by @leepokai in #164

Full Changelog: v2.19.0...v2.19.1