After installing from a Release Package and running start-windows.bat (or the mac/linux equivalent), the terminal experience is rough:
- Log output is JSON (
pythonjsonlogger.JsonFormatter). Right for log shippers, hostile for a fresh user staring at a cmd window.
- The URL the user needs (
http://localhost:8145) is just a stray uvicorn INFO line buried in the JSON wall — you have to read the README or the bundled dist-README.md to know where to point your browser.
Proposed fix (target 0.9.1)
-
LOG_FORMAT=text env var that flips main.py's formatter to readable LEVEL logger: message form. Default off → Docker / make dev keeps JSON for log-shipper ingestion.
-
After uvicorn reports ready, print a clearly-set-off banner:
════════════════════════════════════════════════
✓ RoboScope is running
Open in your browser: http://localhost:8145
════════════════════════════════════════════════
Respects the PORT env var so a custom port shows the right URL.
-
Optional OPEN_BROWSER=1 flag to auto-webbrowser.open() after readiness, default off so headless installs don't break.
-
ASCII-safe fallback when running on Windows with a legacy code page (avoids mojibake).
Full story spec + acceptance criteria: _bmad-output/implementation-artifacts/launch-1-windows-terminal-ux.md.
After installing from a Release Package and running
start-windows.bat(or the mac/linux equivalent), the terminal experience is rough:pythonjsonlogger.JsonFormatter). Right for log shippers, hostile for a fresh user staring at a cmd window.http://localhost:8145) is just a stray uvicorn INFO line buried in the JSON wall — you have to read the README or the bundleddist-README.mdto know where to point your browser.Proposed fix (target 0.9.1)
LOG_FORMAT=textenv var that flipsmain.py's formatter to readableLEVEL logger: messageform. Default off → Docker /make devkeeps JSON for log-shipper ingestion.After uvicorn reports ready, print a clearly-set-off banner:
Respects the
PORTenv var so a custom port shows the right URL.Optional
OPEN_BROWSER=1flag to auto-webbrowser.open()after readiness, default off so headless installs don't break.ASCII-safe fallback when running on Windows with a legacy code page (avoids mojibake).
Full story spec + acceptance criteria:
_bmad-output/implementation-artifacts/launch-1-windows-terminal-ux.md.