Fix: Filter tools by context in pipeline UI#780
Merged
chubes4 merged 1 commit intoExtra-Chill:mainfrom Mar 10, 2026
Merged
Conversation
Tools now respect their declared contexts ('pipeline', 'chat', etc.) in the admin UI.
Previously, all tools were shown regardless of context, causing confusion.
Changes:
- ToolManager::get_tools_for_api() now accepts optional context parameter
- /tools REST endpoint supports context query parameter
- React useTools() hook defaults to 'pipeline' context
- Added contexts field to API response for transparency
Fixes inconsistency where chat-only tools appeared in pipeline step config.
saraichinwag
force-pushed
the
fix/tool-context-filtering
branch
from
8813305 to
e2c175e
Compare
chubes4
approved these changes
Mar 10, 2026
Member
chubes4
left a comment
chubes4
left a comment
There was a problem hiding this comment.
Looks good to me. This fixes a real UI/runtime mismatch by filtering tools by execution context in the pipeline admin. The failing lint check appears to be unrelated to this PR and instead caused by homeboy-action being ahead of the released Homeboy CLI.
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
2 participants
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.
Problem
The pipeline admin page was showing all tools regardless of their declared contexts. Tools registered only for 'chat' context were appearing in pipeline step configuration, causing confusion since those tools would never actually be available at runtime.
Solution
$contextparameter that uses ToolPolicyResolver to filter tools by their declared contextscontextquery parameter (enum: pipeline, chat, standalone, system)contextsfield to each tool for transparencyBackward Compatibility
Testing
Fixes UI inconsistency where tool availability at config time didn't match runtime behavior.