Repository navigation
v1.7.1
Changed
- session_start is now off on the webhook by default, like every other channel. The default config already turned off the toast, ntfy and the terminal bell for a new session, but not the webhook, so anyone with a webhook enabled (Slack, Discord, Telegram, generic) got a "session started" post on every new agent session. Your config is deep-merged over the defaults: if you never set
events.session_start.webhookEnabled, those posts stop after you upgrade; if you set it totrue, nothing changes. To get them back, add"events": { "session_start": { "webhookEnabled": true } }to~/.anotifier/config.json(theanotifier configprompts have no per-event webhook setting).
Fixed
- On Windows, a usage or context warning lock released by another chat at the same moment is no longer logged as an EPERM error in
anotifier status.
What's Changed
- test(notify): fire the duplicate claude runs together in the dedup bell test by @AminDhouib in #89
- docs(landing): anotifier 1.7.0, ntfy fallback server by @AminDhouib in #91
- fix(alerts): retry the lock once when a Windows EPERM race outruns the stat by @AminDhouib in #92
- fix(config): session_start is off on the webhook by default, like every other channel by @AminDhouib in #93
- chore(release): 1.7.1 by @AminDhouib in #94
Full Changelog: v1.7.0...v1.7.1