docs: update the providers page for openai-compatible, registerProvider and provider imports
维护者通常 1 天内回复
@prakashNalla 已经在做这个了。
开始于 2026年10月21日。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 76/100
- Issue 类型
- 文档
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- markdown, typescript
调研方向
Read website/src/content/docs/core/providers.mdx alongside packages/core/src/types.ts and ProviderConfig to check the options table. Use packages/core/tests/providers/openai-compatible.test.ts and registry.test.ts for working examples, and review packages/core/src/providers/registry.ts, base.ts, and packages/server/src/config.ts for registration and custom provider behavior. Update the listed sections and examples, then verify them with the website build and add the empty changeset described in the issue.
由索引模型根据 Issue 内容生成。
描述
Three provider changes landed this week and the providers page doesn't know about any of them yet: the openai-compatible type and registerProvider() (#289), the provider classes moving to their own import paths (#288), and the server taking a provider object you built yourself. This issue brings website/src/content/docs/core/providers.mdx up to date.
What to do
- "Provider configuration" (lines 8 to 31): add an
openai-compatibleblock. Note thatapiKeyis required forclaude,openaiandgemini, and setup fails with a clear error without it. - "Options" table (lines 43 to 53): add
headers(OpenAI and openai-compatible, sent on every request) andsupportsTools(same providers, defaulttrue, tools aren't sent whenfalseand one warning is logged). Change themaxTokensParamrow: the default is'max_completion_tokens'foropenaiand'max_tokens'foropenai-compatible. - "OpenAI-compatible servers" (lines 61 to 83): switch the Ollama and OpenRouter examples to
type: 'openai-compatible'. Ollama needs noapiKeynow, so drop the'ollama'placeholder line. Add one example withheaders(OpenRouter'sHTTP-Refereris a good one) and one withsupportsTools: falsefor a model that can't call tools.baseURLandmodelare required for this type. - New section "Custom providers", after "AIProvider interface":
registerProvider('my-llm', async (config) => new MyProvider(config)), thenprovider: { type: 'my-llm', ... }. The factory gets the whole provider config. Registering a built-in name throws, and registering the same name again replaces it.- The other way: pass the provider object itself as the server's
provider(packages/server/src/config.ts, lines 17 to 20). Anything withstep()orchat()works.
- "Direct provider usage" (lines 112 to 138): add a short note that
ClaudeProvider,OpenAIProviderandGeminiProviderare imported from@chatcops/core/providers/claude,/openaiand/gemini, not from@chatcops/core, so importing core doesn't load all three SDKs.
Where to look
packages/core/src/types.ts,ProviderConfigpackages/core/src/providers/registry.tsandbase.ts(createProvider)packages/core/tests/providers/openai-compatible.test.tsandregistry.test.tsfor working configs
Acceptance criteria
- Every option in
ProviderConfigis in the Options table, and nothing that isn't - Every code sample on the page matches the current types (copy them into a scratch
.tsfile inpackages/coreand runpnpm --filter @chatcops/core typecheck, then delete it) -
pnpm --filter @chatcops/website buildsucceeds - Changeset:
pnpm changeset --empty(docs only)
Please get this merged by Dec 8, since the v0.6 release notes link to it.
Want to work on this? Comment below and I'll assign it to you. Please take one issue at a time, branch off dev, and open your PR against dev with Closes #<this issue number>. Setup notes (pnpm, build before test) are in CONTRIBUTING.md.
- 主要语言
- TypeScript
- 星标
- 13
- 派生
- 7
- 平均合并
- 3 小时 33 分钟
- 30 天内合并 PR
- 176
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
codercops/chatcops 的其他 Issue
-
Add startup checks that catch weak or leaked security settings可能已有人在做 @varun-pahuja 于 2 天前认领。 未关闭enhancement good first issue hacktoberfest server
codercops/chatcops#231 · 3 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Type-check the TypeScript samples in the docs可能已有人在做 @An16og 于 2 天前认领。 未关闭documentation hacktoberfest help wanted testing
难度 4/5 3-5 天 新手友好度 70/100
codercops/chatcops#201 · 7 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
hacktoberfest
难度 1/5 1 小时以内 新手友好度 35/100
维护者通常 1 天内回复
-
Add built-in translations to the widget可能已有人在做 @piyusshhjangid 于 1 天前认领。 未关闭help wanted widget
难度 4/5 3-5 天 新手友好度 52/100
codercops/chatcops#55 · 3 条评论 ·
维护者通常 1 天内回复
查看 codercops/chatcops 的全部 Issue
相似的 Issue
-
area:agent-view area:tui bug platform:macos
难度 2/5 1-3 小时 新手友好度 70/100
anthropics/claude-code#104558 ·
维护者通常 1 天内回复
-
updater
难度 2/5 1-3 小时 新手友好度 68/100
UniversityOfHelsinkiCS/oodikone#5141 ·
-
maintanance
难度 2/5 1-3 小时 新手友好度 74/100
inmanta/web-console#7606 ·
维护者通常 1 天内回复
-
bug skills
难度 2/5 1-3 小时 新手友好度 77/100
equinor/fusion-framework#5846 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 74/100