fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534)

~1500 progress messages across 481 files were using log_warn (yellow)
for normal status updates like "Installing...", "Setting up...",
"Creating server...", etc. This made users think something was wrong
when everything was proceeding normally.

Changes:
- Replace log_warn with log_step for all progress/status messages
- Keep log_warn only for actual warnings (errors, remediation hints)
- Remove emoji from 3 sprite completion messages

Agent: ux-engineer

Co-authored-by: A <6723574+louisgv@users.noreply.github.com>
This commit is contained in:
A 2026-02-11 14:37:43 -08:00 committed by GitHub
parent 800e9ed564
commit 0835b35a36
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
481 changed files with 1602 additions and 1602 deletions

View file

@ -38,7 +38,7 @@ CODESPACE_NAME="$CODESPACE"
wait_for_codespace "$CODESPACE"
# 4. Install open-interpreter
log_warn "Installing open-interpreter..."
log_step "Installing open-interpreter..."
run_server "pip install open-interpreter 2>/dev/null || pip3 install open-interpreter"
log_info "open-interpreter installed"
@ -62,7 +62,7 @@ log_info "Codespace: $CODESPACE"
echo ""
# 7. Start interpreter interactively
log_warn "Starting open-interpreter..."
log_step "Starting open-interpreter..."
log_warn "To delete codespace later, run: gh codespace delete --codespace $CODESPACE --force"
echo ""
sleep 1