Onboarding: document the explicit "Start server" step (no more auto-start) - #9
Open
ronaldmannak wants to merge 1 commit into
Open
Onboarding: document the explicit "Start server" step (no more auto-start)#9ronaldmannak wants to merge 1 commit into
ronaldmannak wants to merge 1 commit into
Conversation
The onboarding Ready page no longer auto-starts the server. Update the
Install and Run guide to the current four-step wizard and the explicit
Start server / Open Chat flow.
- Rewrite "Start the server" as Welcome -> Model -> Access -> Ready, with
the explicit "Start server" button as the single commit point.
- Refresh Welcome copy ("Set up Pico") and access choices ("This Mac only"
vs "Devices on my local network") to match shipping strings.
- Remove the stale claim that onboarding sets "Open at login" and
"Prevent sleep" (no longer part of the reduced flow).
- Add a troubleshooting entry for the Ready step's "Try again" failure.
Grounded in ronaldmannak/PicoServer OnboardingWizardView.swift at
origin/main (PicoServer #59, #73).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HUy41ab4FDBpeUukzGfN57
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
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
2 participants
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
Keeps the Install and Run getting-started page in sync with the onboarding rework merged in
ronaldmannak/PicoServersince the last documentation run. All facts are grounded in the current source (OnboardingWizardView.swiftatorigin/main), not point-in-time PR descriptions.The headline change: onboarding no longer auto-starts the server. The Ready page now has an explicit
Start serverbutton as the single commit point, thenOpen Chat(PicoServer #73). The Welcome/Access copy was also refreshed (PicoServer #59). The page inmasterstill described a pre-wizard flow that setOpen at login/Prevent sleepand implied auto-start, so it was stale on both counts.What changed
Start serverbutton the point where the server actually starts. Added the note that navigating the wizard never starts or stops the server.Open Chatnow documents the WebUI hand-off, including the download-progress page shown when a model is still downloading.This Mac only(binds127.0.0.1) vsDevices on my local network(binds0.0.0.0) with the nested Bonjour option, matching the shipping strings.Open at loginandPrevent sleep(no longer part of the reduced flow), and refreshed the Welcome button toSet up Pico.Try againfailure state (port already in use / server didn't respond).Evidence
Verified against
ronaldmannak/PicoServerorigin/mainat177b0c14(after #73's merge):OnboardingWizardView.swift'sWizardPageset (welcome/models/access/ready), the.continueTitle("Set up Pico")Welcome button,readyContinueTitle(Start server/Starting…/Open Chat/Restart server/Try again), thestartServerFromButton()single-commit-point (save → start → reachability probe),recordStartFailure's "didn't respond on port …" message, andAccessPage's two options + nested Bonjour toggle.Not done on purpose
httpServerTaskafter terminal failure) — a cosmetic contrast tweak and an internal restart-cycle bug fix, respectively; no user-, admin-, or developer-facing surface to document.Relationship to the other open documentation PRs
This routine has opened one branch/PR per run, so several overlapping onboarding doc PRs are open against
masterand awaiting human review. This PR carries the newest truth:install-and-runonboarding paragraph.Recommendation for the maintainer: land one onboarding PR (this one, as the most current) and close the older overlapping onboarding PRs (#5, #6, #7); keep #4 and #8 independent.
Generated by Claude Code