Files
paseo/packages
paseo-bot[bot]andClaude Opus 5.5 4fb95106e7 Notify once while an agent's finish is unread, not on each turn it starts on its own (#10200)
* fix(server): notify once while an agent's finish is unread

Since v0.16.0, a turn that an agent starts on its own cleared the
agent's unread "finished" attention. Every such turn that then ended
raised a new "finished" notification. A Claude Code agent that reacts
to each event of a Monitor or a background task starts one turn per
event, so the user got a notification every few seconds.

A turn that the agent starts on its own now clears only error
attention, which is what the earlier change intended. An unread finish
stays unread, so the next finish does not notify again. After the
user reads the agent, the next finish notifies as before. A prompt
from the user still clears all attention.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(server): notify a repeat finish the user was not told about

The previous commit kept an unread finish across turns that an agent
starts on its own, and the agent manager then sent no attention for
the later finishes. Suppose the user had the agent on screen for the
first finish. The app keeps that finish unread, and no notification
is sent while the agent is on screen. After the user left, no later
finish notified at all.

The agent manager now reports each finish, and marks a finish that
repeats an unread finish. The websocket server owns delivery, so it
records whether it delivered a notification for the unread finish.
A repeat notifies only when nothing was delivered for it yet.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(server): key the notified unread finish by its attention timestamp

The websocket server recorded only that it had notified for some
finish of an agent. Mark as unread starts a new unread finish without
an attention event, so a later repeat used the record of an older
finish that the user had already read, and sent nothing.

The attention callback now carries the timestamp of the agent's
current unread attention, which identifies the unread finish. The
server stores the timestamp it notified for, and suppresses a finish
only when it belongs to that same unread finish. This replaces the
repeatsUnreadFinish flag.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: paseo-bot[bot] <266920839+paseo-bot[bot]@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-19 11:08:01 +00:00
..