Your order follows you to the table: beady-eye's plugin 0.4.0 tells a session about the beads it is working on, unasked

Put a session's id in a bead's agent_session metadata, and the beady-eye plugin tells that session of every change to the bead, as if it had called watch. It hears about each pull request gate on the bead too, and the beads that gate holds back, so a pull request's reviews, checks and merge reach the session that is working on it. Nobody had to write the order down twice.

claude plugin marketplace add CodeForBreakfast/beady-eye#plugin-v0.4.0
claude plugin install beady-eye@beady-eye

Pin the marketplace to the new release and update the plugin. bdi and the plugin can go in either order.

Claim it, and you're on the ticket

Here a session has claimed dun-7 and written its own id onto it. It never called watch. When the gate on pull request #12 closes, this lands in the session all the same:

<channel source="beady-eye" project="dunwich" id="dun-8" status="closed" ready="false">
dun-8 in dunwich, "Merge of #12", has changed.
- Its status went from open to closed.
</channel>
<channel source="beady-eye" project="dunwich" id="dun-7" status="open" ready="true">
dun-7 in dunwich, "Sign the elder ward", has changed.
- It became ready.
</channel>

If your bdi config sets agent_session_key under [join], the plugin reads that key instead.

The plates clear themselves

These watches end on their own. A bead stops being watched once it no longer names the session, or once it closes and the session has been told. unwatch leaves such a bead watched while the session still holds it. A bead the session watched for itself as well stays watched until the session unwatches it.

The using-beady-eye skill's description now says it is for subscribing to a bead's changes, so an agent about to sleep and read the bead again finds it first.

Take a seat. Whoever took your order brings it over.