I would use this, but it does not work with a custom provider.
Open
Bugs
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
I would use this, but it does not work with a custom provider. For example, I used a deepseek api key, and it does not work. I can't even use the app at this point.
---
| Field | Value |
| --- | --- |
| App version | 1.1.0 |
| OS | Windows 10.0.26200 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Week 5 |
Contributor guide
Research direction
Start by reproducing the failure in the /chat path using app version 1.1.0 on Windows 10 with a DeepSeek API key configured as a custom provider. Done means the app can be used with that provider, with the failure behavior covered by an appropriate regression check.
Written by the indexing model from the issue text.
Assessment
- Domain
- ai, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100