feat(ai): validate and document Google Gemini via the OpenAI-compatible endpoint
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- java
- Domain
- ai, backend, documentation
Research direction
Read the README provider table and the thrillhousebot.ai.pricing.<model> entries, then trace the existing quarkus-langchain4j-openai configuration for AI_BASE_URL and AI_MODEL. Verify a review end to end against Gemini’s OpenAI-compatible endpoint, add common Gemini model pricing entries and document the listed caveats. Done when the provider setup, caveats, and approximate pricing are documented and the end-to-end review is verified.
Written by the indexing model from the issue text.
Description
Problem Statement
Google Gemini exposes an OpenAI-compatible endpoint (https://generativelanguage.googleapis.com/v1beta/openai/), so it should already work through the existing quarkus-langchain4j-openai path by pointing AI_BASE_URL/AI_MODEL at it — but this is undocumented and unverified, and the cost/feature caveats are not captured.
Proposed Solution
- Verify a review end-to-end against Gemini via the OpenAI-compatible endpoint.
- Add a provider-table row in the README and
thrillhousebot.ai.pricing.<model>entries for common Gemini models. - Document the caveats: Gemini-specific knobs (safety settings, thinking config, explicit caching) ride on
extra_body, which the typed OpenAI client does not pass, and cost is approximate because cached/thinking tokens are not broken out in the OpenAIusageshape. First-class support is tracked separately.
Alternatives Considered
- Wait for native multi-provider support — but the OpenAI-compatible path works today and is worth documenting.
Priority
Important
Code of Conduct
- I have searched for existing issues and this is not a duplicate.
- Dominant language
- Java
- Stars
- 35
- Forks
- 7
- Avg merge
- 9h 37m
- Merged PRs (30d)
- 148
Getting set up
- Ships a 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 devops-thiago/ThrillhouseBot
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
devops-thiago/ThrillhouseBot#1132 ·
Maintainers usually reply within 1 day
-
fix(review): always name the linked issue and its unmet criterion in the summaryPossibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
devops-thiago/ThrillhouseBot#1093 ·
Maintainers usually reply within 1 day
-
documentation enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
devops-thiago/ThrillhouseBot#321 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
devops-thiago/ThrillhouseBot#46 ·
Maintainers usually reply within 1 day
-
fix(dashboard): login page returns 500 in mock mode (window is not defined)Possibly taken @devops-thiago claimed this 1 day ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 30/100
devops-thiago/ThrillhouseBot#1128 ·
Maintainers usually reply within 1 day
All issues in devops-thiago/ThrillhouseBot
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
scylladb/scylla-cdc-source-connector#350 ·
Maintainers usually reply within 1 day
-
agent:working documentation enhancement go:build lane:needs-decision
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Sanne/incus-spawn#1435 · 3 comments ·
Maintainers usually reply within 1 day
-
area:shuffle bug priority:high requires-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
apache/datafusion-comet#7062 ·
Maintainers usually reply within 1 day
-
wait for review
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
enhancement good first issue up-for-grabs
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
AnikethTS/ChangeRadar#22 ·
Maintainers usually reply within 1 day