Repository navigation
Conversation
Contributor
Author
|
@greptileai review this draft. This documents the proposed behavior in agentsfleet/agentsfleet#792; the changelog entry is marked coming soon. |
indykish
marked this pull request as ready for review
November 1, 2026 09:00
This branch has not been deployed
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 fleet-tools reference omits reviewed HTTP egress modes and redirected job-log reads. Document the saved policy, three-hop/30-second GET limit, header removal and completeness notices. Both new capabilities remain marked coming soon.
Companion source: agentsfleet feature branch, checked at
a83a4f957958d9985fd7419955ee8cf484633801.Session notes 1
Added the HTTP settings and download reference, with defaults, package domains and allow-list bounds. Corrected existing browser-availability and Slack-delivery claims while checking the whole page against version
0.71.0.The HTTP switches preserve sandbox access; existing
allowentries retain their conditional sandbox effect. This documentation supplies no deployment or acceptance result.Review
Scoped standards and native adversarial findings are fixed:
fleets/tools.mdx: distinguish reviewed hosts from enabled package domains, qualify optional content type, and narrow the sandbox guarantee to the two new HTTP switches.fleets/tools.mdx: describe current browser-tool unavailability and possible final Slack-delivery failure.fleets/tools.mdx: state the 64-entry/255-character bounds and refresh source-checked metadata.changelog.mdx: add the customer-visible lead and keep the entry within its prose budget.Make
93901fe0df3a2ba215821dd265d707c4b1e5eece, isolated checkout:make test— exit 0; 25 tests,OK, documentation check passed.orly doctor— exit 0; installed rules match.orly gate work— exit 0; 25 tests,OK.orly gate pratb610427ea04dad678c3c7692a4257124796d3abb— exit 0;make lintexit 0, OpenAPI drift clean, build validation passed, no broken links found.

Confidence Score: 5/5
The documentation changes appear safe to merge.Summary
Documents upcoming HTTP access settings and guarded downloads.
No actionable issues were established.
Reviews (2) · Last reviewed commit: "docs(m235): distinguish HTTP switches fr..." · Reviewed by Greptile