Repository navigation
docs: use official PyPI for the local runtime example - #17
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.
The documented local agent-loop setup pinned the public a2 server but still used the caller's configured package index. Select official PyPI explicitly, matching current CI and avoiding stale mirrors. The shared command serves both languages.
Validation: fresh Python environment installed public
agent-sandbox-server==0.4.0a2using the documented command; pip check, npm ci, typecheck, all 24 tests, actual four-step local HTTP loop, npm pack dry-run and scoped record links/diff checks passed. Owned local server exited after SIGTERM. No cloud resources, runtime/API changes, package version changes or npm publication.Engineering decision and actual local evidence are included. Remote CI/review remain delivery gates. This follows the user's request to keep maintained installation instructions consistent with current public packages.