Repository navigation
feat(agents): add secure fetch native tool - #17
Merged
Merged
Conversation
This was referenced Jul 24, 2026
konglyyy
marked this pull request as ready for review
July 24, 2026 10:40
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.
Summary
http.fetch.getworkspace-native Agent toolValidation
npm run validatewith an isolated PostgreSQL 16 database: 852 tests passedRelated PRs and merge order
Documentation
Updates contract documentation and includes a completed execution plan. User-facing documentation is delivered in the related docs PR.
Residual risk
Live public HTTPS exchange behavior is covered with deterministic policy, DNS, stream, and executor tests rather than a network-dependent test. Production behavior remains subject to the deployment environment DNS resolver and outbound HTTPS policy.