Support hosted skill-only Plugins and capability directories - #5
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.
Hosted environments previously rejected Plugin packages and capability directories. This change lets inline and template configurations install skill-only Plugin ZIPs and snapshot workspace directories after setup. Codex, Claude Code and MiniMax Code load the selected Skills through the shared Runtime contract, preserve package-relative resources, and reuse installed contents during cold continuation.
Core keeps Plugin contents encrypted and public responses metadata-only. Initialization remains owned by the existing allocation lifecycle; Provider operations and native execution loops are unchanged. Plugin MCP and unconfirmed upstream semantics remain documented gaps.
Validation:
make check, SQL/OpenAPI generation, targeted race and real PostgreSQL checks passed.Evidence and limits are recorded in
contracts/agents-api/environment-templates.md. This is partial protocol coverage, not complete Environment Templates compatibility.