Repository navigation
docs: update fleet setup chat guides - #224
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.
Session notes 1
Combined both setup-chat documentation worktrees into one seven-file change.
The guides match the merged recovery and editor behavior; changelog labels use the product PR merge dates.
No product UI source changed, so this docs-only PR has no UI screenshot.
Review
P2
fleets/authoring.mdx:73Recent implied saved chats appear in the sidebar. FIXED — the page now says unsaved setup chats.P2
fleets/authoring.mdx:79Rename omitted unresolved provider usage. FIXED — the page names pending usage checks.Final adversarial pass: No findings. The Oct 21 and Oct 23 changelog labels match merged PRs #779 and #783.
Make
bun run orly gate verify— exit 0; docs language clean, 25 documentation tests passed, OpenAPI drift clean, Mintlify build validated, no broken links.git diff --check— exit 0.gitleaks protect --staged— exit 0; no leaks found.gstack-gate-diff main— exit 0; listed=0, eligible=0, inspected=0, unread=0.gstack-banned-terms check --base main— exit 0; no banned-terms file configured.gh pr view 779 --repo agentsfleet/agentsfleet— exit 0; merged 2026-10-21T03:55:06Z.gh pr view 783 --repo agentsfleet/agentsfleet— exit 0; merged 2026-10-23T02:53:07Z.bun run slop:diff origin/main— unavailable; the docs repo has noslop:diffscript.bun run orly gate pr— pre-push exit 1; its only red item wasgit.pushed, which required the reviewed commit on the remote. The remote branch now points to the reviewed commit. No post-push gate was run per the user's instruction.orly-babysit-prs— not run; no post-push polling per the user's instruction.Session notes 2
Aligned the authoring error reference with the recovery guide.
UZ-AUTHOR-008now covers rejected credentials;UZ-AUTHOR-015directs users to stop the uncertain reply before sending again and notes the accounting hold;UZ-AUTHOR-016explains that accounting is resolved and a new message can retry.Review
Greptile P2
fleets/authoring.mdx:61-65: FIXED in7a19f33. The error-code advice now matches the authoring guide and runtime recovery behavior.Adversarial review of the PR diff: no findings.
Make
orly gate verify— pre-push exit 0; docs language,make lint, 25 documentation tests, OpenAPI drift, Mintlify build, and broken-link checks passed.git diff --check— exit 0.gitleaks protect --staged --redact— no leaks found.

Confidence Score: 5/5
The PR appears safe to merge; the previous recovery-guidance mismatch is fixed.Summary
Updates the fleet guides for setup chats beside the conversation.
No new actionable issues were found in the changes since the previous review.
Reviews (2) · Last reviewed commit: "docs: align authoring error recovery gui..." · Reviewed by Greptile