Forking a session doesn't provide any visual indication of ongoing progress o...
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
Forking a session doesn't provide any visual indication of ongoing progress or asynchronous execution (other than printing the "forking session" message). There is also no noticiation when the forking is finished.
---
| Field | Value |
| --- | --- |
| App version | 1.0.22 |
| OS | Windows 10.0.26200 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Week 18 |
Contributor guide
Research direction
Start by reproducing the session fork flow on the /chat path using app version 1.0.22 and observe the current "forking session" message. Identify where the fork begins and finishes, then define done as a visible indication during asynchronous execution and a notification when forking completes.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100