feat: index autorouter captures by agentId for multi-agent gateway#8
Merged
Conversation
Adds a second in-memory index keyed by a derived agent identifier (env OPENCLAW_AGENT_ID/RUN_ID first, then trailing path segment of agentDir/workspaceDir — "workspace" -> "main", "workspace-new-agent-3" -> "new-agent-3"). Extends the taas.autorouter.lastRoute RPC to accept { agentId } and prefer the agent-keyed lookup. Studio passes its known agentId so each agent gets ITS routing metadata in a multi-agent gateway process. Smoke test covers the new path.
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
1 participant
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.
Follows up #7. The previous capture map was keyed only by the plugin-derived sessionId, which the Studio cannot easily reconstruct because it does not know each agent gateway-side workspace dir. Add an agentId-keyed alias derived from agentDir/workspaceDir (workspace -> main, workspace-X -> X) or OPENCLAW_AGENT_ID env. The taas.autorouter.lastRoute RPC now accepts { agentId } and prefers the agent-keyed lookup so multi-agent gateways serve each agent the correct routing metadata.