Notification rules don't wait on you anymore, and cope with a lost connection.
Notification rules
- Waiting for you: when a reply needs your OK and you don't answer within a minute (or the phone is locked), it goes into a list instead of holding up every other chat. One quiet notification and a banner on the Chats screen; each reply shows their messages and the draft, with Send, Edit and Skip. If they wrote again or you answered yourself in the meantime, it says so. The waiting reply also shows in its chat, with the same buttons.
- A reply isn't sent anymore when the person writes again before it goes out (even during the countdown): the next run answers everything in one reply. One reply per run, and none once you've answered yourself.
- Without internet, rules wait and start by themselves when the connection is back. A run that fails on a network error goes once more and doesn't count toward the hourly limit, and messages that waited are answered knowing they're not new.
- Nothing is dropped quietly anymore: up to 30 chats can wait their turn, and if more write at once, a notification says who wasn't handled.
Fixes
- An approval only covers the chat that asked for it, and only the exact message or link it named. Before, an OK given in one chat could cover a different action in another one for ten minutes, including a notification rule's reply.
- Approval cards no longer time out after a minute: Claude Code and Codex gave up on a phone tool after 60 seconds, so an agent could report "timed out" while its card was still waiting. Buddy's agents now wait up to 10 minutes, and the "Phone tools in your own sessions" commands set the same (run the new command again to get it).
- "Couldn't check OpenCode: String index out of range: -1" on slow phones (#9).
Updating
Buddy will tell you about this update (or ask any agent "update yourself"). Otherwise install buddy.apk below over your current Buddy; your chats, settings and sign-ins are kept.
Full Changelog: v2.2.3...v2.2.4