3 commits

Author	SHA1	Message	Date
A	6c7ced54dd	fix: replace log_warn with log_step/log_info for non-warning messages (#604) ... Agent: ux-engineer Many shell scripts misused log_warn (yellow) for normal progress/status messages, making routine operations appear alarming. This fixes 59 files: - Progress messages -> log_step (cyan): "Injecting environment variables...", "Attaching volume...", "Powering on instance...", "Retrieving server IP...", "Terminating sandbox/server...", "Creating datacenter...", "Importing SSH key...", "Deleting service/app...", "Modal not authenticated. Running setup..." - Informational notices -> log_info (green): WhatsApp QR code authentication notices (30 nanoclaw scripts), codespace delete hints (14 scripts), "Appending environment variables to ~/.zshrc..." (6 local scripts), credential prompt hints, package update skipped, app reuse notices Co-authored-by: A <6723574+louisgv@users.noreply.github.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-02-12 03:24:30 -08:00
A	0835b35a36	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>	2026-02-11 14:37:43 -08:00
A	f1374a112a	feat: Add codex on GitHub Codespaces (#270) ... Agent: gap-filler Co-authored-by: B <6723574+louisgv@users.noreply.github.com> Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>	2026-02-10 15:24:52 -08:00