ux: fix install and upgrade success messages by la14-1 · Pull Request #1113 · OpenRouterLabs/spawn

la14-1 · 2026-02-14T17:12:29Z

Summary

Fix install script escape codes not rendering properly in success message
Fix confusing "Run your spawn command again" message after explicit spawn update
Bump CLI version to 0.2.82

Fixes

Test Plan

Manual test: Run install script and verify "Run spawn to get started" renders properly
Manual test: Run spawn update and verify message says "Run spawn again" (not "your spawn command")
Syntax check: bash -n cli/install.sh passes
Version bump: 0.2.81 → 0.2.82

🤖 Generated by ux-engineer

Fixes two UX issues identified in #1106: 1. Install script: Raw escape codes weren't rendering in log_info - Before: "Run \033[1mspawn\033[0m\033[0;32m to get started\033[0m" - After: Uses printf with proper color variable interpolation 2. Update command: Confusing message after `spawn update` - Before: "Run your spawn command again to use the new version" - After: "Run spawn again to use the new version" - The word "your" implied the user had run some other command, but they explicitly ran `spawn update` Agent: ux-engineer Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

louisgv

Security Review

Verdict: APPROVED

Findings

No security issues found. This is a minimal UX-only change:

cli/install.sh:104 — Replaced log_info with printf for the "get started" message. Only hardcoded string literals and color variables; no user-controlled input flows into the format string.
cli/src/commands.ts:1736-1737 — Simplified update success/info messages. Pure string literal changes.
cli/package.json — Version bump 0.2.81 → 0.2.82 (correct per policy).

Tests

bash -n: PASS
bun test: 3 pre-existing failures (unrelated to this PR, same on main), all other tests PASS
curl|bash: OK (source fallback pattern unchanged)
macOS compat: OK (printf usage is correct, no echo -e)

-- security/pr-reviewer

la14-1 · 2026-02-14T17:12:29Z

Summary

Fix install script escape codes not rendering properly in success message
Fix confusing "Run your spawn command again" message after explicit spawn update
Bump CLI version to 0.2.82

Fixes

Closes#1106

Test Plan

Manual test: Run install script and verify "Run spawn to get started" renders properly
Manual test: Run spawn update and verify message says "Run spawn again" (not "your spawn command")
Syntax check: bash -n cli/install.sh passes
Version bump: 0.2.81 → 0.2.82

🤖 Generated by ux-engineer

Fixes two UX issues identified in #1106: 1. Install script: Raw escape codes weren't rendering in log_info - Before: "Run \033[1mspawn\033[0m\033[0;32m to get started\033[0m" - After: Uses printf with proper color variable interpolation 2. Update command: Confusing message after `spawn update` - Before: "Run your spawn command again to use the new version" - After: "Run spawn again to use the new version" - The word "your" implied the user had run some other command, but they explicitly ran `spawn update` Agent: ux-engineer Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

louisgv

Security Review

Verdict: APPROVED

Findings

No security issues found. This is a minimal UX-only change:

cli/install.sh:104 — Replaced log_info with printf for the "get started" message. Only hardcoded string literals and color variables; no user-controlled input flows into the format string.
cli/src/commands.ts:1736-1737 — Simplified update success/info messages. Pure string literal changes.
cli/package.json — Version bump 0.2.81 → 0.2.82 (correct per policy).

Tests

bash -n: PASS
bun test: 3 pre-existing failures (unrelated to this PR, same on main), all other tests PASS
curl|bash: OK (source fallback pattern unchanged)
macOS compat: OK (printf usage is correct, no echo -e)

-- security/pr-reviewer

la14-1 · 2026-02-14T17:12:29Z

Summary

Fix install script escape codes not rendering properly in success message
Fix confusing "Run your spawn command again" message after explicit spawn update
Bump CLI version to 0.2.82

Fixes

Closes#1106

Test Plan

Manual test: Run install script and verify "Run spawn to get started" renders properly
Manual test: Run spawn update and verify message says "Run spawn again" (not "your spawn command")
Syntax check: bash -n cli/install.sh passes
Version bump: 0.2.81 → 0.2.82

🤖 Generated by ux-engineer

Fixes two UX issues identified in #1106: 1. Install script: Raw escape codes weren't rendering in log_info - Before: "Run \033[1mspawn\033[0m\033[0;32m to get started\033[0m" - After: Uses printf with proper color variable interpolation 2. Update command: Confusing message after `spawn update` - Before: "Run your spawn command again to use the new version" - After: "Run spawn again to use the new version" - The word "your" implied the user had run some other command, but they explicitly ran `spawn update` Agent: ux-engineer Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

louisgv

Security Review

Verdict: APPROVED

Findings

No security issues found. This is a minimal UX-only change:

cli/install.sh:104 — Replaced log_info with printf for the "get started" message. Only hardcoded string literals and color variables; no user-controlled input flows into the format string.
cli/src/commands.ts:1736-1737 — Simplified update success/info messages. Pure string literal changes.
cli/package.json — Version bump 0.2.81 → 0.2.82 (correct per policy).

Tests

bash -n: PASS
bun test: 3 pre-existing failures (unrelated to this PR, same on main), all other tests PASS
curl|bash: OK (source fallback pattern unchanged)
macOS compat: OK (printf usage is correct, no echo -e)

-- security/pr-reviewer

la14-1 · 2026-02-14T17:12:29Z

Summary

Fix install script escape codes not rendering properly in success message
Fix confusing "Run your spawn command again" message after explicit spawn update
Bump CLI version to 0.2.82

Fixes

Closes#1106

Test Plan

Manual test: Run install script and verify "Run spawn to get started" renders properly
Manual test: Run spawn update and verify message says "Run spawn again" (not "your spawn command")
Syntax check: bash -n cli/install.sh passes
Version bump: 0.2.81 → 0.2.82

🤖 Generated by ux-engineer

Fixes two UX issues identified in #1106: 1. Install script: Raw escape codes weren't rendering in log_info - Before: "Run \033[1mspawn\033[0m\033[0;32m to get started\033[0m" - After: Uses printf with proper color variable interpolation 2. Update command: Confusing message after `spawn update` - Before: "Run your spawn command again to use the new version" - After: "Run spawn again to use the new version" - The word "your" implied the user had run some other command, but they explicitly ran `spawn update` Agent: ux-engineer Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

louisgv

Security Review

Verdict: APPROVED

Findings

No security issues found. This is a minimal UX-only change:

cli/install.sh:104 — Replaced log_info with printf for the "get started" message. Only hardcoded string literals and color variables; no user-controlled input flows into the format string.
cli/src/commands.ts:1736-1737 — Simplified update success/info messages. Pure string literal changes.
cli/package.json — Version bump 0.2.81 → 0.2.82 (correct per policy).

Tests

bash -n: PASS
bun test: 3 pre-existing failures (unrelated to this PR, same on main), all other tests PASS
curl|bash: OK (source fallback pattern unchanged)
macOS compat: OK (printf usage is correct, no echo -e)

-- security/pr-reviewer

la14-1 · 2026-02-14T17:12:29Z

Summary

Fix install script escape codes not rendering properly in success message
Fix confusing "Run your spawn command again" message after explicit spawn update
Bump CLI version to 0.2.82

Fixes

Closes#1106

Test Plan

Manual test: Run install script and verify "Run spawn to get started" renders properly
Manual test: Run spawn update and verify message says "Run spawn again" (not "your spawn command")
Syntax check: bash -n cli/install.sh passes
Version bump: 0.2.81 → 0.2.82

🤖 Generated by ux-engineer

Fixes two UX issues identified in #1106: 1. Install script: Raw escape codes weren't rendering in log_info - Before: "Run \033[1mspawn\033[0m\033[0;32m to get started\033[0m" - After: Uses printf with proper color variable interpolation 2. Update command: Confusing message after `spawn update` - Before: "Run your spawn command again to use the new version" - After: "Run spawn again to use the new version" - The word "your" implied the user had run some other command, but they explicitly ran `spawn update` Agent: ux-engineer Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

louisgv

Security Review

Verdict: APPROVED

Findings

No security issues found. This is a minimal UX-only change:

cli/install.sh:104 — Replaced log_info with printf for the "get started" message. Only hardcoded string literals and color variables; no user-controlled input flows into the format string.
cli/src/commands.ts:1736-1737 — Simplified update success/info messages. Pure string literal changes.
cli/package.json — Version bump 0.2.81 → 0.2.82 (correct per policy).

Tests

bash -n: PASS
bun test: 3 pre-existing failures (unrelated to this PR, same on main), all other tests PASS
curl|bash: OK (source fallback pattern unchanged)
macOS compat: OK (printf usage is correct, no echo -e)

-- security/pr-reviewer

la14-1 · 2026-02-14T17:12:29Z

Summary

Fix install script escape codes not rendering properly in success message
Fix confusing "Run your spawn command again" message after explicit spawn update
Bump CLI version to 0.2.82

Fixes

Closes#1106

Test Plan

Manual test: Run install script and verify "Run spawn to get started" renders properly
Manual test: Run spawn update and verify message says "Run spawn again" (not "your spawn command")
Syntax check: bash -n cli/install.sh passes
Version bump: 0.2.81 → 0.2.82

🤖 Generated by ux-engineer

Fixes two UX issues identified in #1106: 1. Install script: Raw escape codes weren't rendering in log_info - Before: "Run \033[1mspawn\033[0m\033[0;32m to get started\033[0m" - After: Uses printf with proper color variable interpolation 2. Update command: Confusing message after `spawn update` - Before: "Run your spawn command again to use the new version" - After: "Run spawn again to use the new version" - The word "your" implied the user had run some other command, but they explicitly ran `spawn update` Agent: ux-engineer Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

louisgv

Security Review

Verdict: APPROVED

Findings

No security issues found. This is a minimal UX-only change:

cli/install.sh:104 — Replaced log_info with printf for the "get started" message. Only hardcoded string literals and color variables; no user-controlled input flows into the format string.
cli/src/commands.ts:1736-1737 — Simplified update success/info messages. Pure string literal changes.
cli/package.json — Version bump 0.2.81 → 0.2.82 (correct per policy).

Tests

bash -n: PASS
bun test: 3 pre-existing failures (unrelated to this PR, same on main), all other tests PASS
curl|bash: OK (source fallback pattern unchanged)
macOS compat: OK (printf usage is correct, no echo -e)

-- security/pr-reviewer

la14-1 · 2026-02-14T17:12:29Z

Summary

Fix install script escape codes not rendering properly in success message
Fix confusing "Run your spawn command again" message after explicit spawn update
Bump CLI version to 0.2.82

Fixes

Closes#1106

Test Plan

Manual test: Run install script and verify "Run spawn to get started" renders properly
Manual test: Run spawn update and verify message says "Run spawn again" (not "your spawn command")
Syntax check: bash -n cli/install.sh passes
Version bump: 0.2.81 → 0.2.82

🤖 Generated by ux-engineer

Fixes two UX issues identified in #1106: 1. Install script: Raw escape codes weren't rendering in log_info - Before: "Run \033[1mspawn\033[0m\033[0;32m to get started\033[0m" - After: Uses printf with proper color variable interpolation 2. Update command: Confusing message after `spawn update` - Before: "Run your spawn command again to use the new version" - After: "Run spawn again to use the new version" - The word "your" implied the user had run some other command, but they explicitly ran `spawn update` Agent: ux-engineer Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

louisgv

Security Review

Verdict: APPROVED

Findings

No security issues found. This is a minimal UX-only change:

cli/install.sh:104 — Replaced log_info with printf for the "get started" message. Only hardcoded string literals and color variables; no user-controlled input flows into the format string.
cli/src/commands.ts:1736-1737 — Simplified update success/info messages. Pure string literal changes.
cli/package.json — Version bump 0.2.81 → 0.2.82 (correct per policy).

Tests

bash -n: PASS
bun test: 3 pre-existing failures (unrelated to this PR, same on main), all other tests PASS
curl|bash: OK (source fallback pattern unchanged)
macOS compat: OK (printf usage is correct, no echo -e)

-- security/pr-reviewer

la14-1 · 2026-02-14T17:12:29Z

Summary

Fix install script escape codes not rendering properly in success message
Fix confusing "Run your spawn command again" message after explicit spawn update
Bump CLI version to 0.2.82

Fixes

Closes#1106

Test Plan

Manual test: Run install script and verify "Run spawn to get started" renders properly
Manual test: Run spawn update and verify message says "Run spawn again" (not "your spawn command")
Syntax check: bash -n cli/install.sh passes
Version bump: 0.2.81 → 0.2.82

🤖 Generated by ux-engineer

Fixes two UX issues identified in #1106: 1. Install script: Raw escape codes weren't rendering in log_info - Before: "Run \033[1mspawn\033[0m\033[0;32m to get started\033[0m" - After: Uses printf with proper color variable interpolation 2. Update command: Confusing message after `spawn update` - Before: "Run your spawn command again to use the new version" - After: "Run spawn again to use the new version" - The word "your" implied the user had run some other command, but they explicitly ran `spawn update` Agent: ux-engineer Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

louisgv

Security Review

Verdict: APPROVED

Findings

No security issues found. This is a minimal UX-only change:

cli/install.sh:104 — Replaced log_info with printf for the "get started" message. Only hardcoded string literals and color variables; no user-controlled input flows into the format string.
cli/src/commands.ts:1736-1737 — Simplified update success/info messages. Pure string literal changes.
cli/package.json — Version bump 0.2.81 → 0.2.82 (correct per policy).

Tests

bash -n: PASS
bun test: 3 pre-existing failures (unrelated to this PR, same on main), all other tests PASS
curl|bash: OK (source fallback pattern unchanged)
macOS compat: OK (printf usage is correct, no echo -e)

-- security/pr-reviewer

louisgv mentioned this pull request Feb 14, 2026
[Bug]: install and upgrade "to get started" is botched! #1106
Closed