Repository navigation
Remove SandboxAQ Foundry agent; keep AQCat and AQPotency MCP agents - #231
Open
sravankumarux wants to merge 4 commits into
Open
sravankumarux wants to merge 4 commits into
sravankumarux wants to merge 4 commits into
Conversation
sandboxaq: - Remove the "Which SandboxAQ agent do I want?" table. - Fix the image build step: the Dockerfile is in tools/sandboxaq-model/, so build from there, with --platform linux/amd64 as other catalog agents do (the tool runs on x86-64 Azure VMs). - Fence the architecture diagram and bracket the support email. aqcat, aqpotency: - Drop the link to the sandboxaq agent.
This was referenced Oct 9, 2026
github-actions
Bot
added
3p-contribution
- Build from the repository root via agents/sandboxaq with the tool directory as the build context, so the starting directory is explicit. - Describe the sensitive-data behavior as agent instructions rather than platform-enforced controls; the agent runs with human-in-the-loop and tool confirmation disabled.
github-actions
Bot
added
3p-contribution
sravankumarux
marked this pull request as ready for review
October 9, 2026 18:26
Catalog will ship only the MCP-based AQCat and AQPotency agents.
sravankumarux
changed the title
Contributor
Author
|
Updated the scope of this PR. We're going with the MCP route only for SandboxAQ, so this now removes the Foundry-model sandboxaq agent added in #193 instead of fixing its README. What changed: Removed agents/sandboxaq/ (agent definition, README, and the sandboxaq-model tool container). Please take another look when you get a chance. |
github-actions
Bot
added
3p-contribution
Replace the header-credential and service-token guidance with per-user OAuth sign-in, note that the agents cannot connect from Discovery until it supports per-user MCP sign-in, and describe the Foundry redirect URL requirement.
github-actions
Bot
removed
3p-contribution
github-actions
Bot
added
3p-contribution
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.
Summary
Removes the Foundry-model
sandboxaqagent added in #193. SandboxAQ will be listed in the catalog only through the MCP-basedaqcatandaqpotencyagents. Replaces #229 and #230.Changes
agents/sandboxaq/: removed (agent definition, README, and thesandboxaq-modeltool container).agents/aqcat/README.md,agents/aqpotency/README.md: drop the link to thesandboxaqagent.No other files reference
agents/sandboxaq.Status
SandboxAQ's Azure AI Foundry onboarding is in progress. AQCat is partway through onboarding (the publisher plan and asset replication are not yet complete), and AQPotency is on hold pending CPU pricing support.