Skip to content

Route sq agent-tools through the Blox tools proxy - #44

Closed
luispadron wants to merge 1 commit into
block:mainfrom
luispadron:luis/agent-tools-blox-proxy-900311
Closed

luispadron wants to merge 1 commit into
block:mainfrom
luispadron:luis/agent-tools-blox-proxy-900311

Conversation

@luispadron

Copy link
Copy Markdown

On BuilderLab Blox workstations where BL_TOOLS_BASE_URL is set, sq agent-tools now defaults to that endpoint and delegates authentication to Roxy, the same way bl tools does. Top-level help still uses the embedded catalog, and backend selection is unchanged when BL_TOOLS_BASE_URL is absent.

When an extension can't be inspected, BuilderLab backends now point users at their portal's Connections page instead of G2, and a link in the server response is surfaced when present.

On Blox workstations with BL_TOOLS_BASE_URL set, sq agent-tools now
defaults to that endpoint and delegates authentication to Roxy, as
bl tools does. Inaccessible-extension errors point BuilderLab backends
at their Connections page instead of G2.
@luispadron
luispadron force-pushed the luis/agent-tools-blox-proxy-900311 branch from 33efdee to 8926e59 Compare November 4, 2026 15:47
@luispadron

Copy link
Copy Markdown
Author

🤖 Closing without merging: the Blox workstation route will use bl tools instead, so sq agent-tools needs no change.

@luispadron luispadron closed this Nov 4, 2026
@luispadron
luispadron deleted the luis/agent-tools-blox-proxy-900311 branch November 4, 2026 18:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant