so it seems there is a race when new worktree is used + custom agent.
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Description
so it seems there is a race when new worktree is used + custom agent. if worktree is not ready before copilot trying to read the custom agent, session fails.
| Field | Value |
|---|---|
| App version | 1.1.20 |
| OS | Windows 10.0.26200 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Week 10 |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. First reproduce the failure on Windows 10 with app version 1.1.20 using a new worktree and a custom agent, then trace the session startup ordering; done means the session succeeds when the worktree is not initially ready.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop, developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100