Document more OpenAI-compatible providers in the README
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 62/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript, markdown, nodejs, ollama, threejs
- Domain
- documentation
Research direction
The base URL table lives in the README, so start there and read the existing rows for Ollama, LM Studio, OpenRouter and Groq to match their format. Add rows only for providers you have tested, giving the base URL, a working model name and whether send page images is supported. Done means the table has new rows with each value confirmed by a real request, and the PR says which providers were tested.
Written by the indexing model from the issue text.
Description
What problem would this solve?
The README lists base URLs for Ollama, LM Studio, OpenRouter and Groq. Many people use other servers (for example DeepSeek, Mistral, Together, vLLM) and don't know what to type in the Base URL box.
What would you like to happen?
Add rows to the base URL table in the README for providers you have actually tried. For each one: the base URL, an example model name that works, and whether it accepts page images (send page images). Only add what you tested, and mention it in your PR. Docs only, no code needed.
Alternatives you've considered
No response
Contribution
- I'd like to work on this myself
- Dominant language
- JavaScript
- Stars
- 8
- Forks
- 1
- Avg merge
- 17m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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.
More from AlphaaCode/Popbook
-
enhancement good first issue help wanted
Difficulty 2/5 Half a day Newbie friendliness 66/100
AlphaaCode/Popbook#10 · 1 comment ·
-
documentation help wanted
Difficulty 1/5 1-3 hours Newbie friendliness 62/100
AlphaaCode/Popbook#8 ·
-
enhancement help wanted scene block
Difficulty 3/5 1-2 days Newbie friendliness 58/100
AlphaaCode/Popbook#9 ·
All issues in AlphaaCode/Popbook
Similar issues
-
[ordering-review] workshop order graph: 1 confirmed ordering problem, 3 cycles are false positivesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
githubnext/gh-aw-workshop#5331 ·
Maintainers usually reply within 1 day
-
Remove: 21 SexturyOpenchannels:remove check:passed
Difficulty 1/5 Under an hour Newbie friendliness 65/100
Maintainers usually reply within 4 days
-
[vika] console keeps a stale "in progress" turn after a daemon restart mid-runPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
volcengine/OpenViking#7011 ·
Maintainers usually reply within 1 day
-
__VERSION__ within dist build is not replaced, causes missing version in XDM implementation detailsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Issue: ready for confirmation Reported on 2.4.9 Triage: Dev.Experience
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
magento/magento2#41773 · 1 comment ·
Maintainers usually reply within 5 days