You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Project creation asks for the workspace twice after choosing Canvas or Studio #21
Selecting a workspace in the Projects page's New project dialog does not create the project. It opens a second page that asks the user to choose Studio or Canvas again.
Reproduced against current main (d2ef270, BeatDesign 0.2.4) in Chrome on Windows. No provider key or generation is needed.
Steps to reproduce
Open Projects and click New project.
In Choose where to begin, choose Start in Canvas.
Instead of entering a new Canvas project, the app opens /canvas and displays Start a new project / Choose Studio or Canvas to create this project, with another Studio/Canvas choice.
The same duplicate selection occurs after choosing Start in Studio.
Expected behavior
Choosing Canvas or Studio in the dialog should create one shared project and open the selected view directly. During creation, repeated clicks should not create additional projects. A failed attempt should be retryable in the originally selected view.
Direct visits to /canvas or /studio should remain read-only until an explicit create action. That entry can offer a single button for its known workspace, rather than asking the user to select the other workspace again. Locale, model and prompt parameters should survive creation.
Likely cause and proposed fix
CreateProjectDialog in src/components/home/workspace-page.tsx uses links to /studio and /canvas, so the first selection only navigates.
CreateProjectRoutePage receives workspaceMode from its route loader but does not use it to resolve the entry action.
The route page's error retry currently calls createProject('studio') even if the user originally chose Canvas.
I propose sharing the existing project-creation request and pending/retry handling between these two surfaces, creating directly from the dialog, and keeping direct entry explicitly tied to its route. This change does not need new providers, schema changes or generation behavior.
Implementation PR: #22 — fix: create projects directly after selecting a workspace.
The PR is based directly on upstream main and contains only the project-creation flow, translations, documentation and regression tests. Its description records the local validation and unchanged Windows baseline failures.
Before: after choosing Canvas in the Projects dialog, the app asks for the workspace again.
After: one choice creates a project and opens Canvas directly. The screenshots use the upstream-based branch and an empty test project.
Activity
JaysonAlbert commentedon Oct 17, 2026
Implementation PR: #22 — fix: create projects directly after selecting a workspace.
The PR is based directly on upstream
mainand contains only the project-creation flow, translations, documentation and regression tests. Its description records the local validation and unchanged Windows baseline failures.Before: after choosing Canvas in the Projects dialog, the app asks for the workspace again.
After: one choice creates a project and opens Canvas directly. The screenshots use the upstream-based branch and an empty test project.