feat: make workspace name optional and auto-generate a name when empty

[benoitf]

Context

PR #2575 (merged as #2518 fix) made the project folder optional when creating a workspace. However, the workspace name field is still required — the "Continue" button stays disabled until a name is entered.

When creating a sandbox-only workspace (no project folder), there's no source path to derive a default name from, so the user is forced to type one manually every time.

Problem

The current flow requires the user to provide a workspace name before they can proceed. This adds unnecessary friction, especially for sandbox-only workspaces where a meaningful name may not be known upfront.

Proposal

Make the workspace name optional. When the user leaves it empty:

• Auto-generate a name (e.g., workspace-happy-turtle)
• This is consistent with how openshell already generates workspace names

The unique-username-generator package could be used for name generation.

Note: the project already uses random-words for flow name generation (see FlowCreate.svelte), so reusing that package instead is also an option to avoid adding a new dependency.

Affected areas

• UI validation (AgentWorkspaceCreate.svelte): the isCurrentStepComplete check requires getEffectiveWorkspaceName() !== ''
• Backend validation (agent-workspace-manager.ts): throws 'workspace name is required when no project folder is specified'
• Both need to support generating a name when none is provided

[coderabbitai]

🔗 Related PRs

#2355 - fix(agent-workspace): make model mandatory in create workspace [merged]
#2449 - fix(agent-workspace): prevent workspace rename [merged]
#2464 - fix(agent-workspace): validate workspace name against hostname limit [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 2:54 PM UTC · Completed 2:57 PM UTC
Commit: 85891ca · View workflow run →

[fullsend-ai-triage]

Triage Summary

Update: The previously identified blocker (PR #2575 — "allow creating empty workspaces without a project folder") has now been merged. This issue is unblocked and ready for implementation.

Problem

When creating a sandbox-only workspace, the workspace name field is required but there is no project folder path to derive a default name from. This forces manual name entry every time, adding unnecessary friction.

Recommended Approach

• UI (AgentWorkspaceCreate.svelte): Update isCurrentStepComplete so an empty name does not block the Continue button
• Backend (agent-workspace-manager.ts): Replace the error on missing workspace name with auto-generation logic
• Name generation: Reuse the existing random-words package (already used in FlowCreate.svelte) to avoid adding a new dependency. Generate names in a pattern consistent with openshell conventions

Proposed Test Cases

1. Backend: when no name is provided and no project folder is set,
   auto-generate a valid workspace name (not throw an error)
2. Backend: auto-generated name must satisfy hostname character/length
   constraints (per #2464)
3. UI: isCurrentStepComplete returns true when name field is empty
4. Edge case: when a project folder IS provided but name is empty,
   verify a name is still auto-generated or derived from the folder

Previous run

Triage Summary

This is a clear and well-specified feature request. The proposal to auto-generate workspace names when none is provided is straightforward, and the affected code areas are precisely identified.

However, PR #2575 ("feat: allow creating empty workspaces without a project folder") is still open and has not been merged yet. The issue body references it as already merged, but it is currently in OPEN state. Since the primary use case for this feature — sandbox-only workspaces with no project folder to derive a name from — depends on the functionality introduced by PR #2575, that PR is a prerequisite for this work.

Once PR #2575 lands, the path forward is clear:

• UI (AgentWorkspaceCreate.svelte): Remove the requirement that getEffectiveWorkspaceName() !== '' for step completion; generate a fallback name when the field is left empty
• Backend (agent-workspace-manager.ts): Replace the error thrown when workspace name is missing with auto-generation logic
• Name generation: The random-words package is already used in FlowCreate.svelte for flow names — reusing it avoids adding a new dependency

Marking as blocked on PR #2575.

Blocked by:

• feat: allow creating empty workspaces without a project folder #2575

[fbricon]

/fs-triage

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 4:11 PM UTC · Completed 4:14 PM UTC
Commit: 7a80556 · View workflow run →