Add a quick “test model connection” button
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
When a custom LLM endpoint fails, it is hard to know if the problem is the key, model name, base URL, timeout, or response format. A tiny test button in Settings could send a minimal prompt and return a readable diagnostic. This would save a lot of trial and error.
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
Start by locating the Settings UI and the code that sends requests to custom LLM endpoints. Trace how connection errors, keys, model names, base URLs, timeouts, and response formats are currently handled. Done means a Settings button sends a minimal prompt and returns a readable diagnostic for these failure cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100