Community provider example: HAL SUPREME OpenAI-compatible peer (OpenCode-shaped JSON)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 85/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript, nodejs, typescript
- Domain
- ai-infra-agents, documentation
Research direction
Look for the community provider examples or documentation section in the OpenCode repository, likely in a docs folder or a providers configuration guide. The PR should add the provided JSON block to the appropriate example file. Verify the structure matches existing examples and that the models and options are correctly formatted. Running any documentation tests or linting will ensure the change is ready.
Written by the indexing model from the issue text.
Description
Hi OpenCode maintainers,
I'm Jakob (UniteAndCreateForLife). HAL SUPREME is a free/community AI companion with an OpenAI-compatible peer gateway at https://api.halsupreme.com/v1 (Bearer; placeholders only).
Our peer-join docs already use an OpenCode-shaped @ai-sdk/openai-compatible provider block. Soft ask: would a community provider example / docs mention be welcome? Happy to open a small PR with this shape (no secrets):
{
"provider": {
"hal-supreme": {
"npm": "@ai-sdk/openai-compatible",
"name": "HAL SUPREME",
"options": {
"baseURL": "https://api.halsupreme.com/v1",
"apiKey": "<HAL_GATEWAY_TOKEN>"
},
"models": {
"hal-fast": { "name": "hal/fast" },
"hal-coder": { "name": "hal/coder" },
"hal-deep": { "name": "hal/deep" },
"hal-council": { "name": "hal/council" }
}
}
}
}
If Issues isn't the right channel, point me at Discussions/docs. No rush — just aligning open peer meshes.
https://halsupreme.com | https://discord.gg/GnufdBbyg | https://github.com/UniteAndCreateForLife/hal-supreme-community
Thanks for OpenCode.
- Jakob / UniteAndCreateForLife
- Dominant language
- TypeScript
- Stars
- 210k
- Forks
- 27.8k
- Avg merge
- 8h 43m
- Merged PRs (30d)
- 380
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 anomalyco/opencode
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
anomalyco/opencode#51159 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
All issues in anomalyco/opencode
Similar issues
-
module-request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
appandflow/stim#1604 · 1 comment ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 92/100
lingdojo/kana-dojo#31060 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
paperclipai/paperclip#14173 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day