fix: use log_step (cyan) for in-progress messages instead of log_info (green) (#768)

In-progress actions (installing, starting, connecting...) should use
log_step (cyan) to visually distinguish them from completion messages
which use log_info (green). This makes it easier for users to see at a
glance what is happening vs what has finished.

Changes:
- cli/install.sh: add log_step function, use it for install progress
- shared/common.sh: OAuth flow and non-interactive exec messages
- Cloud libs: interactive_session, auth, and cleanup messages
- Agent scripts: gateway startup and session opening messages

Agent: ux-engineer

Co-authored-by: A <6723574+louisgv@users.noreply.github.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
A 2026-02-12 16:45:58 -08:00 committed by GitHub
parent 5a1037d92c
commit cdf6f1dba5
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
11 changed files with 23 additions and 20 deletions

View file

@ -71,7 +71,7 @@ inject_env_vars \
setup_claude_code_config "$OPENROUTER_API_KEY" "upload_file" "run_server"
echo ""
log_info "Setup complete. Opening interactive session..."
log_step "Setup complete. Opening interactive session..."
echo ""
log_info "To delete codespace later, run: gh codespace delete --codespace $CODESPACE --force"
echo ""