-
Notifications
You must be signed in to change notification settings - Fork 570
refactor(controller): invoke agents directly in MCP handler #1855
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
onematchfox
wants to merge
2
commits into
kagent-dev:main
Choose a base branch
from
onematchfox:refactor-mcp-agent-invocation
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,58 @@ | ||
| package a2a | ||
|
|
||
| import ( | ||
| "context" | ||
| "fmt" | ||
| "sync" | ||
|
|
||
| a2aclient "trpc.group/trpc-go/trpc-a2a-go/client" | ||
| "trpc.group/trpc-go/trpc-a2a-go/protocol" | ||
| ) | ||
|
|
||
| // AgentClientRegistry maps agent route keys to their A2A clients. | ||
| // The A2ARegistrar populates it; the MCP handler reads from it to invoke | ||
| // agents without an HTTP round trip through the controller's own A2A listener. | ||
| type AgentClientRegistry struct { | ||
| mu sync.RWMutex | ||
| clients map[string]*a2aclient.A2AClient | ||
| } | ||
|
|
||
| func NewAgentClientRegistry() *AgentClientRegistry { | ||
| return &AgentClientRegistry{clients: make(map[string]*a2aclient.A2AClient)} | ||
| } | ||
|
|
||
| // set stores the client under the agent's route key (e.g. "namespace/name" or | ||
| // "sandboxes/namespace/name"). | ||
| func (r *AgentClientRegistry) set(agentRef string, c *a2aclient.A2AClient) { | ||
| r.mu.Lock() | ||
| defer r.mu.Unlock() | ||
| r.clients[agentRef] = c | ||
| } | ||
|
|
||
| // delete removes the client for the given agent route key. | ||
| func (r *AgentClientRegistry) delete(agentRef string) { | ||
| r.mu.Lock() | ||
| defer r.mu.Unlock() | ||
| delete(r.clients, agentRef) | ||
| } | ||
|
|
||
| // Register adds or replaces the A2A client for the given agent. It is the | ||
| // exported counterpart of set, intended for use in tests and explicit | ||
| // registrations outside the A2ARegistrar lifecycle. | ||
| func (r *AgentClientRegistry) Register(namespace, name string, c *a2aclient.A2AClient) { | ||
| r.set(namespace+"/"+name, c) | ||
| } | ||
|
|
||
| // SendMessage invokes an agent directly via its cached A2A client. | ||
| // namespace and name must identify a non-sandbox agent; sandbox agents use a | ||
| // different route key and are not yet reachable via this method. | ||
| func (r *AgentClientRegistry) SendMessage(ctx context.Context, namespace, name string, params protocol.SendMessageParams) (*protocol.MessageResult, error) { | ||
| key := namespace + "/" + name | ||
| r.mu.RLock() | ||
| c, ok := r.clients[key] | ||
| r.mu.RUnlock() | ||
| if !ok { | ||
| return nil, fmt.Errorf("agent %s/%s not found or not ready", namespace, name) | ||
| } | ||
| return c.SendMessage(ctx, params) | ||
| } |
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this can be avoided if we just construct the client registry outside of this component and pass it into here AND the mcp handler, what do you think? I personally prefer injecting dependencies that way.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's funny you say that because that was the way I implemented it initially. However, I ended up refactoring because it felt like the
Registrarshould wholly own theRegistry; rather than viewing this as a dependency, maintaining the registry is a core function of the registrar's job. But, this isn't something I'm too firmly opinionated on so I'm happy to change tact again if you prefer?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer that if it's ok