Repository navigation
Let outside agents post a notice on a thread #23383
thomasfevre
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Outside agents connected over MCP can read and message threads. They cannot leave a notice that does not interrupt the agent.
The only way to surface something today is a user message through
t3_thread_send, and that wakes the agent.T3 already has a
notificationturn item, but only the server or a provider may create one. The dispatch guard says "Notifications must be server- or provider-created queued messages". I propose a small extension:externalkind with an agent name. The item gains optionaltitle,body,tagand aresolutionthat is empty while open.t3_thread_notifyposts one without waking the agent. Read-only clients are refused, like other tools that change the environment.Three generic consumers:
This differs from #21240 and #18104, where the message still reaches the agent (now or on its next run), and from #19500, which is a push sent by the agent itself.
What it looks like with the patch:
We have a working patch with tests (branch). Per CONTRIBUTING.md, we would like maintainer approval of the direction and scope before opening a PR.
All reactions