[Bugs] In use-cases with multi-repo under the same workspace folder, if we opt-in wo...
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
**Mood:** 😔
**Category:** Bugs
In use-cases with multi-repo under the same workspace folder, if we opt-in worktree, the default behavior is create worktree per repo that is exhausting task and unproductive.
---
| Field | Value |
| --- | --- |
| App version | 0.2.34 |
| OS | macOS 26.5.0 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Week 2 |
Contributor guide
Research direction
No files or tests are named. Start by reproducing a multi-repository workspace with worktree opt-in and observe the current per-repository creation behavior; then trace the worktree handling for workspace setup. Done should match the intended workspace-level behavior without requiring an exhausting worktree task for every repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- desktop, developer-experience
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100