Workspace wizard: Continue button disabled with no error message

[serbangeorge-m]

Bug description

When creating a new workspace, if the OpenShell gateway isn't available, the wizard's Continue button on Step 1 never becomes clickable and nothing on screen tells the user why. Meanwhile, a banner on the main workspaces page does explain the problem, but it never reaches the wizard, so anyone who misses that banner is stuck with no clue what's wrong.

Operating system

macOS

Installation Method

None

Version

next (development version)

Steps to reproduce

1. Make sure Podman/Docker is not running.
2. Open Kaiden and go to Agentic Workspaces.
3. Notice the banner at the top of the page: "OpenShell Gateway failed to start" — "Gateway process exited before becoming ready: ... failed to query Docker daemon version ... error (Connect)".
4. Click Create Workspace, fill in a project folder and workspace name on Step 1 ("Workspace").
5. Try to click Continue.

Relevant log output

Additional context

No response

[coderabbitai]

🔗 Related PRs

#2500 - feat: display error when unable to start the OpenShell gateway [merged]
#2501 - feat: support gateway selection for workspaces [merged]
#2575 - feat: allow creating empty workspaces without a project folder [open]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 10:51 AM UTC · Completed 10:54 AM UTC
Commit: e498269 · View workflow run →

[fullsend-ai-triage]

Triage Summary

Problem: When the OpenShell gateway is unavailable (e.g., Docker/Podman not running), the workspace wizard's Continue button on Step 1 is silently disabled with no feedback to the user. The main workspaces page shows a banner about the gateway failure, but this information is not surfaced inside the wizard.

Root cause hypothesis: The wizard validates gateway availability to control the Continue button state but does not render any error or warning when no healthy gateway exists. The gateway health state needs to be propagated into the wizard UI.

Recommended fix: Display an inline error or warning message on Step 1 of the wizard when no gateway is available, explaining that the gateway failed to start and suggesting the user check their container runtime (Docker/Podman). The gateway error state is already available on the main workspaces page, so the wizard component needs to subscribe to or query this status.

Related: Issue #2515 tracks broader gateway state handling, which is complementary but not a blocker for this fix.

Proposed test case:

Scenario: Gateway unavailable shows error in workspace wizard
  Given the OpenShell gateway status is "unavailable" or "errored"
  When the user opens the workspace creation wizard
  Then Step 1 displays a visible warning/error message about the gateway
  And the Continue button is disabled

Scenario: Gateway becomes available clears error
  Given the gateway was previously unavailable
  When the gateway status changes to "available"
  Then the error message is removed
  And the Continue button becomes enabled (once other fields are valid)

[fullsend-ai-coder]

🤖 Finished Code · ✅ Success · Started 10:55 AM UTC · Completed 11:15 AM UTC
Commit: e498269 · View workflow run →