Repository navigation
docs: explain setup progress and command disclosures - #236
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.
Setup chat now explains save and publish progress, links to a saved fleet or a pinned Library revision, and keeps command details in expandable groups. Update the public instructions and changelog to match those controls and the clearer internet-access labels.
Session notes 1
Document the approved chat changes and optional Save/Apply origin metadata. CLI provenance labels apply only to new receipts; existing saved versions retain their general label. No
.enveditor or network-enforcement change is included.The matching agentsfleet implementation PR will be linked here before merge. This documentation accompanies the implementation and should land after it.
Review
No unresolved documentation findings. Source checks covered the setup composer, command outcomes, Library revision links and enforced runner network policy. Initial prose findings were corrected by expanding CLI on first use and splitting an overlong paragraph.
Make
make lint— exit 0: 25 documentation tests passed; documentation and OpenAPI operation drift checks clean; Mintlify validation, broken links and all Markdown link checks passed.orly gate pr— exit 0: branch clean and synchronized with its pushed revision; changed prose clean; documentation verification passed.gitleaks git --staged --redact --no-banner— exit 0, no leaks found.

Confidence Score: 5/5
The documentation appears safe to merge after the matching implementation, as planned.Summary
Updates the setup guides to explain progress messages, confirmed saves, and the separate Open fleet action.
Reviews (4) · Last reviewed commit: "docs: explain full output search and cop..." · Reviewed by Greptile
Session notes 2
Align the quickstart and runner installation guide with the current controls, clear confirmation actions when authoring resumes, and document full-output search and copy. Matching implementation: agentsfleet/agentsfleet#794. Merge this documentation after that implementation.
Review
Both Greptile findings are fixed, answered and resolved: conflicting Instructions/Open fleet directions and the retired Allowlist egress name. Greptile reviewed exact head
cbf48d4c08d3d1ad1699c0a727b2f4655e39cce1with confidence 5/5; two quiet polls retained green checks and zero unresolved threads.Make
orly gate pr— exit 0 at clean, pushed headcbf48d4;make lintpassed 25 documentation tests, OpenAPI drift, Mintlify validation, broken links and Markdown link checks. Log:/tmp/agentsfleet-m224-review/docs-gate-pr-output-followup.log.gitleaks git --redact --no-banner --log-opts=origin/main..HEAD— exit 0, no leaks found.lint,gitleaksandGreptile Review— completed successfully. Mintlify Deployment is skipped before merge.