Repository navigation
feat(web): Start from issue dialog with prefilled composer #3
Description
Activity
- added a parent issue
on Oct 5, 2026 Triage
Verdict: Confirmed on current main (
5cebd3b8). Web/desktop dialog slice is fully specified; implementation is in open PR #5 and is not onmainyet.What I checked
- Parent: feat: start agent work from a GitHub issue #1. Depends on feat(server): resolve GitHub issues and prepare an issue worktree thread #2 (server/contracts).
IssueThreadDialog.tsxmissing onmain;PullRequestThreadDialog.tsxis the model to copy (usePreparePullRequestThreadAction, debounced resolve, Local/Worktree actions).- Open PR #5 stacked on feat(server): resolve GitHub issues and prepare an issue worktree thread #4 claims Fixes feat(web): Start from issue dialog with prefilled composer #3: Start-from-issue dialog, palette + branch-picker entry (
issue 123/ URL; bare#123stays PR), composer prefill viasetPrompt, no auto-send. Manual web pass described in PR (not re-executed here). - Shared opener bug: fix(web): prepared worktrees attach to the project's mapped draft, not the invoking draft #6 (
openOrReuseProjectDraftThreadreuses project-mapped draft). Path/setup shared bugs: fix(server): generated worktree paths collide for repositories with the same folder name #7, fix(server): setup scripts run at the worktree root for subdirectory projects #8.
Not a duplicate of #1/#2. Related series only.
Likely code:
apps/web/src/components/IssueThreadDialog.tsx; source-control client actions beside PR prepare; command palette + branch selector hooks; prompt formatting helper/tests.Fix direction: Complete PR #5 after #4; keep mobile/out-of-scope items out. Prefer fixing or clearly documenting #6 if multi-draft projects are in the acceptance path.
Workaround: Use Checkout pull request flow or paste issue text manually.
Outcome:
ready-for-agent— UI scope and acceptance criteria are agentable; blocked only by merging/stacking with #2/#4.
Generated by Claude Code
Part of the "Start agent work from a GitHub issue" parent issue. See it for the full design.
Depends on sub-issue 1 (server and contracts).
Scope
Web and desktop client only. Desktop wraps web, so no Electron changes are expected.
apps/web/src/components/IssueThreadDialog.tsx, modelled onPullRequestThreadDialog.tsx: debounced resolve, shows title and state, one Start work action that creates a worktree.Client actions next to
usePreparePullRequestThreadActioninapps/web/src/lib/sourceControlActions.ts/state/sourceControlActions.ts.On success:
openOrReuseProjectDraftThread({ branch, worktreePath, envMode: "worktree" }), thensetPromptwith:Entry points: a command palette action Start from issue, and a branch-selector item when the query looks like an issue reference (
issue 123or an issue URL; bare#123stays a PR checkout).Loading, error, and unsupported-host states are shown in the dialog.
Tests
Done when
Focused tests, targeted typecheck and lint pass, and one manual pass in the dev web client confirms the flow end to end.