Dashboard: Create Worktree should match ./iw start behavior #349

New issue

Closed

opened 2026-04-15 08:43:49 +00:00 by mprihoda · 1 comment

mprihoda commented

2026-04-15 08:43:49 +00:00

(Migrated from github.com)

Layer: 1 — Fix the Annoying Stuff
Parent: #343

Problem

The dashboard's "Create Worktree" modal creates a worktree but doesn't fully replicate what ./iw start does — specifically, it doesn't create a tmux session, doesn't register properly with the dashboard, and the resulting worktree may not be immediately usable in the same way.

Solution

Match ./iw start behavior — the dashboard create action should produce the same result as running ./iw start <issue-id> from the terminal
This likely means invoking ./iw start under the hood rather than reimplementing the logic
The UI should show progress/status during creation and handle errors gracefully
After creation, the new worktree should appear immediately in the dashboard with full functionality

**Layer:** 1 — Fix the Annoying Stuff **Parent:** #343 ## Problem The dashboard's "Create Worktree" modal creates a worktree but doesn't fully replicate what `./iw start` does — specifically, it doesn't create a tmux session, doesn't register properly with the dashboard, and the resulting worktree may not be immediately usable in the same way. ## Solution 1. **Match `./iw start` behavior** — the dashboard create action should produce the same result as running `./iw start <issue-id>` from the terminal 2. This likely means invoking `./iw start` under the hood rather than reimplementing the logic 3. The UI should show progress/status during creation and handle errors gracefully 4. After creation, the new worktree should appear immediately in the dashboard with full functionality

claude commented

2026-10-16 06:19:01 +00:00

Member

Intake: duplicate of #477

#477 asks for the same result: iw start and the dashboard make identical worktrees, and a change to what iw start does reaches the browser with no second edit. These are items 1, 2 and 4 of this issue. When #477 is done, this issue is done too. #477 also names the cause, which is two separate orchestrations.

Parts of this issue are now out of date:

The dashboard already creates a terminal workspace and registers the worktree (dashboard/jvm/src/infrastructure/CaskServer.scala, the create endpoint).
Item 3 (progress and errors) is mostly present: CreationErrorView, WorktreeCreationError.toUserFriendly, and the HTMX loading indicator in CreateWorktreeModal.scala.

The remaining gaps are all in the "What has already drifted" list of #477: no session hooks, no effort worktrees, the hard-coded ../<dir> path, and the herdr label.

Note: project-management/efforts/dashboard-control-plane/map.md:372 uses #349 as the tracker for create-worktree-parity. That entry must point to #477.

Intake: duplicate of #477 #477 asks for the same result: `iw start` and the dashboard make identical worktrees, and a change to what `iw start` does reaches the browser with no second edit. These are items 1, 2 and 4 of this issue. When #477 is done, this issue is done too. #477 also names the cause, which is two separate orchestrations. Parts of this issue are now out of date: - The dashboard already creates a terminal workspace and registers the worktree (`dashboard/jvm/src/infrastructure/CaskServer.scala`, the create endpoint). - Item 3 (progress and errors) is mostly present: `CreationErrorView`, `WorktreeCreationError.toUserFriendly`, and the HTMX loading indicator in `CreateWorktreeModal.scala`. The remaining gaps are all in the "What has already drifted" list of #477: no session hooks, no effort worktrees, the hard-coded `../<dir>` path, and the herdr label. Note: `project-management/efforts/dashboard-control-plane/map.md:372` uses #349 as the tracker for `create-worktree-parity`. That entry must point to #477.

claude

2026-10-16 06:19:01 +00:00