Repository navigation
Conversation
RunnerPlugins now keeps the tools plugins add for agent turns and the attention sources that wake agents, and runs those sources against the Runner's running agents. AgentsRunner tells its subscribers when what runs or who holds it changes, so sources and agent commands follow the Runner rather than every Manager change. AgentsService forwards the plugin calls with the calling plugin's context. Behavior is unchanged. Co-authored-by: Larry <627498bd4bd1f281a16431e3c6cce3b5c25b6692798c78672298aefbf2f8f8b5@buzz.block.builderlab.xyz> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Logan Johnson <loganj@squareup.com>
loganj
force-pushed
the
agents-runner-plugins
branch
from
October 28, 2026 15:53
083bd2d to
ff944ed
Compare
Contributor
Author
|
🤖 Closing: this change is now part of #1748, which collects one column of the Manager/Runner split in one PR. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
🤖 This is step 7 of the Manager/Runner split for agents. It is an inert refactor.
What changes
Plugins add two things that run with agents. Tools are functions an agent turn can call, such as
link_prand the Builderlab apps tools. Attention sources are plugin code that watches something and wakes an agent. Both lived inAgentsService, the Manager.RunnerPlugins(runner-plugins.ts) now owns them:addToolchecks andtools();addAttentionSource(with its agent MCP connection and agent commands),attentionProviders(), and running each source against the Runner's running agents.AgentsServicekeeps the publicctx.agentsmethods and forwards each call with the calling plugin's context. So a plugin's tools are still withdrawn when the plugin stops.AgentsRunnernow hassubscribe. It tells subscribers when its running agents change or when an agent's holder changes. Attention sources and agent commands follow that instead of every Manager change, such as a team or classifier update. Those inputs are the only things they read.The code moved without edits, except that it reads the Runner's running list and relay instead of the Manager's.
Why
In a hidden agents page, plugins' agent entries add their tools and sources there, next to the agents that use them. This puts that registry with the Runner, so the hidden page can build it without the Manager. It is also where the Builderlab credential will be served, as a link topic.
Tests
buzz-mcpsuites pass locally (4,431 tests). The only failures are the 3 emoji and avatar-picker tests that always fail in this worktree.🤖 Generated with Claude Code