You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 8c89523
Browse filesBrowse the repository at this point in the historyBrowse files
feat(server): let an agent ring the user with session_notify
Hooks fire for every agent, which is the wrong shape when sub-sessions
report to one orchestrator and only that orchestrator should interrupt a
person. This is a tool instead: the session that decides the user is
needed is the session that rings, and nobody else does.
A ping is a doorbell, not history. It publishes to an in-memory bus that
a new subscribeAttention WebSocket stream fans out to every attached
client, and nothing is written down: the reason the agent rang is already
in its thread, and an event-sourced ping would ring again on the next
reconnect replay. Clients drop a ping older than two minutes and never
ring the same one twice, which is what makes a reconnect quiet.
Each client answers in three ways, because no one of them is enough. A
synthesised tone says "now" to someone in the room, a toast says which
session is asking, and the desktop app raises a real Windows notification,
which is the only part that survives a minimized window. Four sounds,
picked in Settings under Integrations or named per call, and the whole
thing is behind a switch that is server-authoritative like the other agent
grants.
Claude Opus 5 in T3 Code.
Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
0 commit comments