Summary
When the browser UI is open but the local server is unreachable, the existing restart affordance cannot start a new server process.
Observed behavior
- After stopping SymbioSync, the browser tab stays open and correctly shows server-unreachable state.
- The restart button currently assumes an already-running server and only restarts the device manager via API.
- If the server is gone, the browser cannot complete that API call.
Expected behavior
When the UI detects server-unreachable state, the restart affordance should either:
- clearly say it cannot restart because the local server is not running and direct the user to
start.bat, or
- use a safe local launcher/protocol/helper to start a new cmd window with SymbioSync running.
Truth/safety impact
Medium. This is a visible failure-mode surface. It should not pretend restart is possible through a dead server.
Design notes
Normal browser JavaScript cannot safely launch arbitrary local processes. Possible future shapes:
- custom Windows URI handler, e.g.
symbiosync://start
- small local watchdog/launcher service
- explicit desktop shortcut / batch flow only
Acceptance criteria
- In server-unreachable state, UI wording/action matches actual capability.
- If a launcher is implemented, it is local-only and clearly documented.
Summary
When the browser UI is open but the local server is unreachable, the existing restart affordance cannot start a new server process.
Observed behavior
Expected behavior
When the UI detects server-unreachable state, the restart affordance should either:
start.bat, orTruth/safety impact
Medium. This is a visible failure-mode surface. It should not pretend restart is possible through a dead server.
Design notes
Normal browser JavaScript cannot safely launch arbitrary local processes. Possible future shapes:
symbiosync://startAcceptance criteria