Repository navigation
Update bundled ACP agent registry - #625
Merged
Merged
Conversation
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
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.
Automated refresh of
maestro-server/src/assets/registry.jsonfrom the ACP registry CDN.Review the diff as a supply-chain change, not a data blob. Entries here decide which
executable and arguments
maestro-serverspawns, so look at changedpackage,version,args,cmdandarchivevalues.Already validated by the workflow that opened this PR:
agentsarraycargo test -p maestro-serverpasses, so the file still deserializes intoAcpRegistryand every agent resolves to a launch command
GitHub does not run workflows on pull requests opened with
GITHUB_TOKEN, so the checksabove are the ones that ran. Push an empty commit if you want the normal CI run too.
Release Notes: