Repository navigation
feat: explicitly prepare and reuse Express managed API keys - #145
Merged
Merged
Conversation
This was referenced Oct 27, 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
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.
Description
AK/SK-only Express SDK users previously had to provision an API key manually. Add explicit
prepare_api_key(confirm=True)/prepare_api_key_sync(confirm=True), then reuse the private key through the shared abx engine from standard sync/async and ProviderSandbox clients. Existing explicit/E2B API keys retain priority and need no CLI.Refs #143. Requires the CLI operations tracked in Alibaba-Agent-Sandbox/agent-sandbox#202 to land first. Do not close the cross-repository acceptance until both consumers and provider are delivered.
Type of Change
Changes
confirm=Truebefore engine I/O; ordinary SDK/MCP runtime calls never create or renew credentials.Testing
Checklist
Definition of Done
.agents/evidence/verify/2026-10-27-managed-api-key.md.Limitations: optional AK/SK path requires the matching CLI feature; no release publication, Windows ACL claim, alternate-region matrix or independent restricted RAM-user verification. Full server failure reproduces on clean main and after proxy variables are removed; no server implementation is changed here.