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,11 +38,11 @@ CODESPACE_NAME="$CODESPACE"
wait_for_codespace "$CODESPACE"
# 4. Install dependencies and nanoclaw
log_warn "Installing Node.js dependencies..."
log_step "Installing Node.js dependencies..."
run_server "npm install -g tsx"
log_info "tsx installed"
log_warn "Cloning and building nanoclaw..."
log_step "Cloning and building nanoclaw..."
run_server "git clone https://github.com/gavrielc/nanoclaw.git ~/nanoclaw && cd ~/nanoclaw && npm install && npm run build"
log_info "nanoclaw installed"
@ -61,7 +61,7 @@ inject_env_vars \
"ANTHROPIC_BASE_URL=https://openrouter.ai/api"
# 7. Create nanoclaw .env file
log_warn "Configuring nanoclaw..."
log_step "Configuring nanoclaw..."
DOTENV_TEMP=$(mktemp)
chmod 600 "${DOTENV_TEMP}"
track_temp_file "${DOTENV_TEMP}"
@ -79,7 +79,7 @@ log_info "Codespace: $CODESPACE"
echo ""
# 8. Start nanoclaw
log_warn "Starting nanoclaw..."
log_step "Starting nanoclaw..."
log_warn "You will need to scan a WhatsApp QR code to authenticate."
log_warn "To delete codespace later, run: gh codespace delete --codespace $CODESPACE --force"
echo ""