docs: add agent-guided mesh installation runbook - #1003
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
🚧 Files skipped from review as they are similar to previous changes (2)
📝 WalkthroughWalkthroughAdds comprehensive interactive Mesh LLM installation runbooks covering setup, enrollment, topology, diagnostics, harness integration, and completion reporting. The website build now publishes the root runbook as ChangesMesh setup runbook
Estimated code review effort: 4 (Complex) | ~45 minutes Suggested reviewers: Sequence Diagram(s)sequenceDiagram
participant Assistant
participant MeshCLI
participant MainNode
participant AdditionalNode
Assistant->>MeshCLI: start supervised serve with JSON logs
MeshCLI->>MainNode: emit invite token and serve status
Assistant->>AdditionalNode: run generated enrollment block
AdditionalNode->>MainNode: join private mesh
Assistant->>MainNode: poll status and model endpoints
Assistant->>MainNode: run bounded chat completion
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
This pull request is currently a draft. Reviews will not take place until the PR is marked as ready for review. |
There was a problem hiding this comment.
@michaelneale These are my agent review findings, after feeding it to Sol to follow
|
@ndizazzo you want to push some changes and take this one over - mostly I am focussing on the wording to guide the agent, but could use with some eyes on making sure it shows up on website right and does reasonable stuff, so feel free to push away. |
|
@michaelneale SG, generally I try to comment only JIC things are still being worked on, but I can take over if you want to focus elsewhere |
…m issue links - Add a goal->section routing table so single-machine goals (e.g. local coding agent) take a short path instead of the full multi-node mesh runbook. - Instruct assistants to filter `models installed` output down to runnable models, excluding layer-package internals and split shards, and show at most three candidates. Workaround for #1004. - Collapse the GitHub issue reference list into inline pointers; the operational lessons are already folded into the relevant sections.
1da241c to
f68e388
Compare
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@AGENTS.md`:
- Around line 41-42: Update the generated-artifact manifest in AGENTS.md to
include docs/funding.json and docs/.well-known/ alongside the existing docs
entries, matching the Eleventy passthrough copy set. The corresponding entries
in website/AGENTS.md require no direct change because they already provide the
reference manifest.
In `@install.md`:
- Around line 496-498: Update the “Node joins as standby” diagnosis in
install.md to state that standby is expected only when enrollment omitted
--model; otherwise treat it as evidence of a failed serving launch. Regenerate
docs/setup-mesh from the corrected install.md wording at its corresponding
section.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 362a26ef-b518-4afb-82c6-bf5be0f3d29c
📒 Files selected for processing (5)
AGENTS.mddocs/setup-meshinstall.mdwebsite/.eleventy.jswebsite/AGENTS.md
Summary
Status
Draft preserved from the earlier installation-guide work for review and refinement.
Summary by CodeRabbit