- Notifications
You must be signed in to change notification settings - Fork1.1k
fix(coderd): gate AI task notifications on agent ready state#20690
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Merged
+83 −2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
Prevents spammy notifications during agent startup by checking that theagent lifecycle state is 'ready' before sending notifications. Thisensures notifications are only sent when the agent is fully operational,not during initialization when status may fluctuate.Changes:- Add agent lifecycle check to enqueueAITaskStateNotification- Only send notifications when agent.LifecycleState == Ready- Add debug logging when notifications are skipped- Add test coverage for agent lifecycle states (starting, created, ready)- Update existing tests to explicitly set ready state when expecting notificationsFixes spammy notification reports where users receive alerts beforethe agent has finished starting up.
johnstcn approved these changesNov 10, 2025
ssncferreira approved these changesNov 10, 2025
Contributor
ssncferreira left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
LGTM
f2a1a7e intomain 38 checks passed
Uh oh!
There was an error while loading.Please reload this page.
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading.Please reload this page.
Relates tocoder/internal#1098
Currently AgentAPI waits for only 2 seconds worth of identical terminal screen snapshots before deciding a task has entered a "stable" state. We interpret this as becoming "idle", resulting in a notification being triggered. This behavior is not ideal and is ultimately the root cause of our spammy notifications.
Unfortunately, until we move AgentAPI to either use the Claude Code SDK (or ACP wrapper around it), we are unable to easily fix the root cause.
This PR instead waits until the agent is ready before it will send state change notifications. This will at least resolvesome of the complaints about task state notifications being too spammy.
🤖 PR was written by Claude Sonnet 4.5 usingCoder Mux and reviewed by a human 👩