Repository navigation
List configured extensions and connection status in bl tools - #17
Merged
Merged
Conversation
Use authenticated ListExtensions for BuilderLab root help and command discovery. Keep unconnected extensions visible with a status label, while retaining the static catalog for sq agent-tools. Co-authored-by: Steve <e010611543c2fb824246457dab086b3bf8de013fcc516d0b35d88236fc254ae3@buzz.block.builderlab.xyz>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 98c7ee7c95
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Classify failed BuilderLab ListTools requests against the configured backend extensions, including selected-extension help and metadata paths. Load discovery only on failure and preserve the original error if discovery also fails. Keep sq catalog behavior unchanged. Co-authored-by: Steve <e010611543c2fb824246457dab086b3bf8de013fcc516d0b35d88236fc254ae3@buzz.block.builderlab.xyz>
thebillg
approved these changes
Oct 14, 2026
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.
bl toolscurrently displays a compiled extension catalog, so its menu can include extensions absent from the selected backend and does not show whether the caller has connected them.Fetch the configured extensions through authenticated KGoose
ListExtensionsforbl tools,bl tools --help, and root--describe-commands. Keep extensions withauth_satisfied_for_caller = falsevisible and mark their descriptions with[not connected], including unconnected extensions with zero tools. Discovery errors propagate instead of falling back to the static catalog.Selected-extension help and metadata also use live discovery to classify failed
ListToolsrequests. An unconnected extension missing from the embedded catalog now produces a connection error; a name absent from the backend produces an unknown-extension error. Successful lookups require onlyListTools. If discovery also fails, the error retains the original tool lookup failure.Root listing now requires backend access and the existing BuilderLab session or Blox proxy authentication. The separately packaged
sq agent-toolsretains its static catalog. Update the usage documentation and cover the listing, connection labels, authentication, and failure behavior in CLI integration tests.