The fact that session automatically make new copies for the git worktree make...
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
The fact that session automatically make new copies for the git worktree makes this app unusable for me for two reasons:
1) our repository is large (multiple GB), and making a copy for each session both makes new session take forever to spin up, and eats up disk space quickly.
2) this means testing changes is cumbersome, because I need to set up a new local testing environment in the copied directory or manually move the changes.
I like the idea of a desktop app where managing multiple session is easier than the CLI version. But my first impressions are definitely that you have tried to make it beginner friendly by "hiding" complexity, which makes the experience worse for power users.
---
| Field | Value |
| --- | --- |
| App version | 1.1.3 |
| OS | Windows 10.0.26200 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Day 1 |
Contributor guide
Research direction
Start by tracing how sessions create Git worktrees in the desktop app and review the behavior described for large repositories on Windows. Done should provide a way to avoid copying the repository per session while preserving a practical path for testing changes; confirm startup time, disk use, and change testing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100