-
Notifications
You must be signed in to change notification settings - Fork 2
⚡ Bolt: Zero-Allocation Agent ID Matching #193
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
Draft
yacosta738
wants to merge
1
commit into
main
Choose a base branch
from
bolt-optimize-agent-id-matching-3398124886008691996
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.
Draft
Changes from all commits
Commits
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
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.
Behavioral regression: containment against canonical form instead of original filter alias can produce false negatives.
In Path B (filter is a known alias,
config_agent_nameis NOT a known agent), the old code checkedconfig_agent_name.to_lowercase().contains(&filter.to_lowercase()). The new code checksconfig_agent_name.to_lowercase().contains(cf)wherecfis the canonical form offilter. Because aliases like"vs-code","open-code", and"claude-code"are not substrings of their canonical forms ("vscode","opencode","claude"), the behaviour changes:config_agent_namefiltercf"vs-code-server""vs-code""vscode"truefalse"open-code-runner""open-code""opencode"truefalseAny user with a custom agent name that contains a hyphenated/underscored alias but not the canonical form will silently stop matching after this change.
The fix is to fall back to checking against the original filter string (lowercase) when the canonical form doesn't match as a substring, or to keep the original filter containment in Path B and only use canonical comparison in Path A:
🐛 Proposed fix
if let Some(cf) = canonical_mcp_agent_id(filter) { if let Some(ca) = canonical_mcp_agent_id(config_agent_name) { return ca == cf; } - // filter is known, use its canonical (lowercase) form to avoid an allocation - return config_agent_name.to_lowercase().contains(cf); + // Fall back to literal filter substring to preserve legacy matching behaviour + // (e.g. "vs-code-server" should still match filter "vs-code"). + let filter_lower = filter.to_lowercase(); + let name_lower = config_agent_name.to_lowercase(); + return name_lower.contains(cf) || name_lower.contains(filter_lower.as_str()); }Additionally, the comment on line 89 is slightly inaccurate:
config_agent_name.to_lowercase()still performs one allocation; the comment should clarify it avoids allocating the filter string, not all allocations.🤖 Prompt for AI Agents