ux: prioritize ready clouds in 'not yet implemented' errors by la14-1 · Pull Request #1117 · OpenRouterLabs/spawn

la14-1 · 2026-02-14T18:08:11Z

Summary

When a user tries to spawn an agent on an unimplemented cloud, the error message now shows alternative clouds sorted by credential availability. Clouds where credentials are already set are shown first and marked with (ready).

Changes

Modified validateImplementation() to use prioritizeCloudsByCredentials()
Added (ready) marker to suggested commands for clouds with credentials
Added legend explaining the "ready" indicator when applicable

Example

Before:

Error: Claude Code on AWS is not yet implemented.
Claude Code is available on 8 clouds. Try one of these instead:
spawn claude hetzner
spawn claude digitalocean
spawn claude sprite

After:

Error: Claude Code on AWS is not yet implemented.
Claude Code is available on 8 clouds. Try one of these instead:
spawn claude sprite (ready)
spawn claude hetzner
spawn claude digitalocean
ready = credentials already set

Impact

This reduces friction by guiding users toward the path of least resistance when their initial choice isn't available. Users with credentials already set for one or more clouds will see those options first.

🤖 Generated with Claude Code

-- refactor/ux-engineer

When a user tries to spawn an agent on an unimplemented cloud, the error message now shows alternative clouds sorted by credential availability. Clouds where credentials are already set are shown first and marked with "(ready)" to make it obvious which options require no setup. Before: Claude Code is available on 8 clouds. Try one of these instead: spawn claude hetzner spawn claude digitalocean spawn claude sprite After: Claude Code is available on 8 clouds. Try one of these instead: spawn claude sprite (ready) spawn claude hetzner spawn claude digitalocean ready = credentials already set This reduces friction by guiding users toward the path of least resistance when their initial choice isn't available. Agent: ux-engineer Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

louisgv

Security Review

Verdict: APPROVED

Findings

No security issues found. The change is minimal and safe:

hasCloudCredentials only checks env var presence via !!process.env[v], never leaks values
parseAuthEnvVars filters auth strings with strict regex /^[A-Z][A-Z0-9_]{3,}$/, preventing injection
Output is terminal-only (no network, no file I/O, no eval)

Tests

bash -n: N/A (TypeScript only)
bun test: PASS (57 tests, 91 assertions)
curl|bash: N/A
macOS compat: N/A

-- security/pr-reviewer

la14-1 · 2026-02-14T18:08:11Z

Summary

When a user tries to spawn an agent on an unimplemented cloud, the error message now shows alternative clouds sorted by credential availability. Clouds where credentials are already set are shown first and marked with (ready).

Changes

Modified validateImplementation() to use prioritizeCloudsByCredentials()
Added (ready) marker to suggested commands for clouds with credentials
Added legend explaining the "ready" indicator when applicable

Example

Before:

Error: Claude Code on AWS is not yet implemented.
Claude Code is available on 8 clouds. Try one of these instead:
spawn claude hetzner
spawn claude digitalocean
spawn claude sprite

After:

Error: Claude Code on AWS is not yet implemented.
Claude Code is available on 8 clouds. Try one of these instead:
spawn claude sprite (ready)
spawn claude hetzner
spawn claude digitalocean
ready = credentials already set

Impact

This reduces friction by guiding users toward the path of least resistance when their initial choice isn't available. Users with credentials already set for one or more clouds will see those options first.

🤖 Generated with Claude Code

-- refactor/ux-engineer

When a user tries to spawn an agent on an unimplemented cloud, the error message now shows alternative clouds sorted by credential availability. Clouds where credentials are already set are shown first and marked with "(ready)" to make it obvious which options require no setup. Before: Claude Code is available on 8 clouds. Try one of these instead: spawn claude hetzner spawn claude digitalocean spawn claude sprite After: Claude Code is available on 8 clouds. Try one of these instead: spawn claude sprite (ready) spawn claude hetzner spawn claude digitalocean ready = credentials already set This reduces friction by guiding users toward the path of least resistance when their initial choice isn't available. Agent: ux-engineer Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

louisgv

Security Review

Verdict: APPROVED

Findings

No security issues found. The change is minimal and safe:

hasCloudCredentials only checks env var presence via !!process.env[v], never leaks values
parseAuthEnvVars filters auth strings with strict regex /^[A-Z][A-Z0-9_]{3,}$/, preventing injection
Output is terminal-only (no network, no file I/O, no eval)

Tests

bash -n: N/A (TypeScript only)
bun test: PASS (57 tests, 91 assertions)
curl|bash: N/A
macOS compat: N/A

-- security/pr-reviewer

la14-1 · 2026-02-14T18:08:11Z

Summary

When a user tries to spawn an agent on an unimplemented cloud, the error message now shows alternative clouds sorted by credential availability. Clouds where credentials are already set are shown first and marked with (ready).

Changes

Modified validateImplementation() to use prioritizeCloudsByCredentials()
Added (ready) marker to suggested commands for clouds with credentials
Added legend explaining the "ready" indicator when applicable

Example

Before:

Error: Claude Code on AWS is not yet implemented.
Claude Code is available on 8 clouds. Try one of these instead:
spawn claude hetzner
spawn claude digitalocean
spawn claude sprite

After:

Error: Claude Code on AWS is not yet implemented.
Claude Code is available on 8 clouds. Try one of these instead:
spawn claude sprite (ready)
spawn claude hetzner
spawn claude digitalocean
ready = credentials already set

Impact

This reduces friction by guiding users toward the path of least resistance when their initial choice isn't available. Users with credentials already set for one or more clouds will see those options first.

🤖 Generated with Claude Code

-- refactor/ux-engineer

When a user tries to spawn an agent on an unimplemented cloud, the error message now shows alternative clouds sorted by credential availability. Clouds where credentials are already set are shown first and marked with "(ready)" to make it obvious which options require no setup. Before: Claude Code is available on 8 clouds. Try one of these instead: spawn claude hetzner spawn claude digitalocean spawn claude sprite After: Claude Code is available on 8 clouds. Try one of these instead: spawn claude sprite (ready) spawn claude hetzner spawn claude digitalocean ready = credentials already set This reduces friction by guiding users toward the path of least resistance when their initial choice isn't available. Agent: ux-engineer Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

louisgv

Security Review

Verdict: APPROVED

Findings

No security issues found. The change is minimal and safe:

hasCloudCredentials only checks env var presence via !!process.env[v], never leaks values
parseAuthEnvVars filters auth strings with strict regex /^[A-Z][A-Z0-9_]{3,}$/, preventing injection
Output is terminal-only (no network, no file I/O, no eval)

Tests

bash -n: N/A (TypeScript only)
bun test: PASS (57 tests, 91 assertions)
curl|bash: N/A
macOS compat: N/A

-- security/pr-reviewer

la14-1 · 2026-02-14T18:08:11Z

Summary

When a user tries to spawn an agent on an unimplemented cloud, the error message now shows alternative clouds sorted by credential availability. Clouds where credentials are already set are shown first and marked with (ready).

Changes

Modified validateImplementation() to use prioritizeCloudsByCredentials()
Added (ready) marker to suggested commands for clouds with credentials
Added legend explaining the "ready" indicator when applicable

Example

Before:

Error: Claude Code on AWS is not yet implemented.
Claude Code is available on 8 clouds. Try one of these instead:
spawn claude hetzner
spawn claude digitalocean
spawn claude sprite

After:

Error: Claude Code on AWS is not yet implemented.
Claude Code is available on 8 clouds. Try one of these instead:
spawn claude sprite (ready)
spawn claude hetzner
spawn claude digitalocean
ready = credentials already set

Impact

This reduces friction by guiding users toward the path of least resistance when their initial choice isn't available. Users with credentials already set for one or more clouds will see those options first.

🤖 Generated with Claude Code

-- refactor/ux-engineer

When a user tries to spawn an agent on an unimplemented cloud, the error message now shows alternative clouds sorted by credential availability. Clouds where credentials are already set are shown first and marked with "(ready)" to make it obvious which options require no setup. Before: Claude Code is available on 8 clouds. Try one of these instead: spawn claude hetzner spawn claude digitalocean spawn claude sprite After: Claude Code is available on 8 clouds. Try one of these instead: spawn claude sprite (ready) spawn claude hetzner spawn claude digitalocean ready = credentials already set This reduces friction by guiding users toward the path of least resistance when their initial choice isn't available. Agent: ux-engineer Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

louisgv

Security Review

Verdict: APPROVED

Findings

No security issues found. The change is minimal and safe:

hasCloudCredentials only checks env var presence via !!process.env[v], never leaks values
parseAuthEnvVars filters auth strings with strict regex /^[A-Z][A-Z0-9_]{3,}$/, preventing injection
Output is terminal-only (no network, no file I/O, no eval)

Tests

bash -n: N/A (TypeScript only)
bun test: PASS (57 tests, 91 assertions)
curl|bash: N/A
macOS compat: N/A

-- security/pr-reviewer

la14-1 · 2026-02-14T18:08:11Z

Summary

When a user tries to spawn an agent on an unimplemented cloud, the error message now shows alternative clouds sorted by credential availability. Clouds where credentials are already set are shown first and marked with (ready).

Changes

Modified validateImplementation() to use prioritizeCloudsByCredentials()
Added (ready) marker to suggested commands for clouds with credentials
Added legend explaining the "ready" indicator when applicable

Example

Before:

Error: Claude Code on AWS is not yet implemented.
Claude Code is available on 8 clouds. Try one of these instead:
spawn claude hetzner
spawn claude digitalocean
spawn claude sprite

After:

Error: Claude Code on AWS is not yet implemented.
Claude Code is available on 8 clouds. Try one of these instead:
spawn claude sprite (ready)
spawn claude hetzner
spawn claude digitalocean
ready = credentials already set

Impact

This reduces friction by guiding users toward the path of least resistance when their initial choice isn't available. Users with credentials already set for one or more clouds will see those options first.

🤖 Generated with Claude Code

-- refactor/ux-engineer

When a user tries to spawn an agent on an unimplemented cloud, the error message now shows alternative clouds sorted by credential availability. Clouds where credentials are already set are shown first and marked with "(ready)" to make it obvious which options require no setup. Before: Claude Code is available on 8 clouds. Try one of these instead: spawn claude hetzner spawn claude digitalocean spawn claude sprite After: Claude Code is available on 8 clouds. Try one of these instead: spawn claude sprite (ready) spawn claude hetzner spawn claude digitalocean ready = credentials already set This reduces friction by guiding users toward the path of least resistance when their initial choice isn't available. Agent: ux-engineer Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

louisgv

Security Review

Verdict: APPROVED

Findings

No security issues found. The change is minimal and safe:

hasCloudCredentials only checks env var presence via !!process.env[v], never leaks values
parseAuthEnvVars filters auth strings with strict regex /^[A-Z][A-Z0-9_]{3,}$/, preventing injection
Output is terminal-only (no network, no file I/O, no eval)

Tests

bash -n: N/A (TypeScript only)
bun test: PASS (57 tests, 91 assertions)
curl|bash: N/A
macOS compat: N/A

-- security/pr-reviewer

la14-1 · 2026-02-14T18:08:11Z

Summary

When a user tries to spawn an agent on an unimplemented cloud, the error message now shows alternative clouds sorted by credential availability. Clouds where credentials are already set are shown first and marked with (ready).

Changes

Modified validateImplementation() to use prioritizeCloudsByCredentials()
Added (ready) marker to suggested commands for clouds with credentials
Added legend explaining the "ready" indicator when applicable

Example

Before:

Error: Claude Code on AWS is not yet implemented.
Claude Code is available on 8 clouds. Try one of these instead:
spawn claude hetzner
spawn claude digitalocean
spawn claude sprite

After:

Error: Claude Code on AWS is not yet implemented.
Claude Code is available on 8 clouds. Try one of these instead:
spawn claude sprite (ready)
spawn claude hetzner
spawn claude digitalocean
ready = credentials already set

Impact

This reduces friction by guiding users toward the path of least resistance when their initial choice isn't available. Users with credentials already set for one or more clouds will see those options first.

🤖 Generated with Claude Code

-- refactor/ux-engineer

When a user tries to spawn an agent on an unimplemented cloud, the error message now shows alternative clouds sorted by credential availability. Clouds where credentials are already set are shown first and marked with "(ready)" to make it obvious which options require no setup. Before: Claude Code is available on 8 clouds. Try one of these instead: spawn claude hetzner spawn claude digitalocean spawn claude sprite After: Claude Code is available on 8 clouds. Try one of these instead: spawn claude sprite (ready) spawn claude hetzner spawn claude digitalocean ready = credentials already set This reduces friction by guiding users toward the path of least resistance when their initial choice isn't available. Agent: ux-engineer Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

louisgv

Security Review

Verdict: APPROVED

Findings

No security issues found. The change is minimal and safe:

hasCloudCredentials only checks env var presence via !!process.env[v], never leaks values
parseAuthEnvVars filters auth strings with strict regex /^[A-Z][A-Z0-9_]{3,}$/, preventing injection
Output is terminal-only (no network, no file I/O, no eval)

Tests

bash -n: N/A (TypeScript only)
bun test: PASS (57 tests, 91 assertions)
curl|bash: N/A
macOS compat: N/A

-- security/pr-reviewer

la14-1 · 2026-02-14T18:08:11Z

Summary

When a user tries to spawn an agent on an unimplemented cloud, the error message now shows alternative clouds sorted by credential availability. Clouds where credentials are already set are shown first and marked with (ready).

Changes

Modified validateImplementation() to use prioritizeCloudsByCredentials()
Added (ready) marker to suggested commands for clouds with credentials
Added legend explaining the "ready" indicator when applicable

Example

Before:

Error: Claude Code on AWS is not yet implemented.
Claude Code is available on 8 clouds. Try one of these instead:
spawn claude hetzner
spawn claude digitalocean
spawn claude sprite

After:

Error: Claude Code on AWS is not yet implemented.
Claude Code is available on 8 clouds. Try one of these instead:
spawn claude sprite (ready)
spawn claude hetzner
spawn claude digitalocean
ready = credentials already set

Impact

This reduces friction by guiding users toward the path of least resistance when their initial choice isn't available. Users with credentials already set for one or more clouds will see those options first.

🤖 Generated with Claude Code

-- refactor/ux-engineer

When a user tries to spawn an agent on an unimplemented cloud, the error message now shows alternative clouds sorted by credential availability. Clouds where credentials are already set are shown first and marked with "(ready)" to make it obvious which options require no setup. Before: Claude Code is available on 8 clouds. Try one of these instead: spawn claude hetzner spawn claude digitalocean spawn claude sprite After: Claude Code is available on 8 clouds. Try one of these instead: spawn claude sprite (ready) spawn claude hetzner spawn claude digitalocean ready = credentials already set This reduces friction by guiding users toward the path of least resistance when their initial choice isn't available. Agent: ux-engineer Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

louisgv

Security Review

Verdict: APPROVED

Findings

No security issues found. The change is minimal and safe:

hasCloudCredentials only checks env var presence via !!process.env[v], never leaks values
parseAuthEnvVars filters auth strings with strict regex /^[A-Z][A-Z0-9_]{3,}$/, preventing injection
Output is terminal-only (no network, no file I/O, no eval)

Tests

bash -n: N/A (TypeScript only)
bun test: PASS (57 tests, 91 assertions)
curl|bash: N/A
macOS compat: N/A

-- security/pr-reviewer

la14-1 · 2026-02-14T18:08:11Z

Summary

When a user tries to spawn an agent on an unimplemented cloud, the error message now shows alternative clouds sorted by credential availability. Clouds where credentials are already set are shown first and marked with (ready).

Changes

Modified validateImplementation() to use prioritizeCloudsByCredentials()
Added (ready) marker to suggested commands for clouds with credentials
Added legend explaining the "ready" indicator when applicable

Example

Before:

Error: Claude Code on AWS is not yet implemented.
Claude Code is available on 8 clouds. Try one of these instead:
spawn claude hetzner
spawn claude digitalocean
spawn claude sprite

After:

Error: Claude Code on AWS is not yet implemented.
Claude Code is available on 8 clouds. Try one of these instead:
spawn claude sprite (ready)
spawn claude hetzner
spawn claude digitalocean
ready = credentials already set

Impact

This reduces friction by guiding users toward the path of least resistance when their initial choice isn't available. Users with credentials already set for one or more clouds will see those options first.

🤖 Generated with Claude Code

-- refactor/ux-engineer

When a user tries to spawn an agent on an unimplemented cloud, the error message now shows alternative clouds sorted by credential availability. Clouds where credentials are already set are shown first and marked with "(ready)" to make it obvious which options require no setup. Before: Claude Code is available on 8 clouds. Try one of these instead: spawn claude hetzner spawn claude digitalocean spawn claude sprite After: Claude Code is available on 8 clouds. Try one of these instead: spawn claude sprite (ready) spawn claude hetzner spawn claude digitalocean ready = credentials already set This reduces friction by guiding users toward the path of least resistance when their initial choice isn't available. Agent: ux-engineer Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

louisgv

Security Review

Verdict: APPROVED

Findings

No security issues found. The change is minimal and safe:

hasCloudCredentials only checks env var presence via !!process.env[v], never leaks values
parseAuthEnvVars filters auth strings with strict regex /^[A-Z][A-Z0-9_]{3,}$/, preventing injection
Output is terminal-only (no network, no file I/O, no eval)