openclaw / openclaw/openclaw-windows-node
UX for switching chats/sessions isn't super clear
Open
Nobody has claimed this yet.
clawsweeper:needs-maintainer-review
clawsweeper:needs-product-decision
clawsweeper:no-new-fix-pr
impact:ux-friction
issue-rating: 🌊 off-meta tidepool
P1
stale
- Dominant language
- C#
- Stars
- 2.1k
- Forks
- 295
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 99
Description
@joelagnel
Contributor guide
No contributing guide indexed for this repository
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 code entry point is named. Start by reproducing the Windows companion suite's chat/session switching flow and clarify the intended UX with the issue author; the payload does not define what completion should look like.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- design, desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100