Can the openai slot be used against a host that issues no key?
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 52/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- python
调研方向
Start by reading builtin_providers.py and tracing how provider, base_url, and api_key from an agent node reach the OpenAI and Gemini clients. Compare the custom BASE_URL case in issue #666 and the MiniMax provider in pull #594. Done should be a clear implementation or documentation decision for keyless OpenAI-compatible hosts, with the resulting behavior verified.
由索引模型根据 Issue 内容生成。
描述
ChatDev reaches a model through a provider name. builtin_providers.py registers openai and gemini with a label and a summary each, provider is a required field on an agent node, base_url is there to override the endpoint, and the client is built from the node config. The gemini client only passes a key when one is set, while the OpenAI client is always built with whatever api_key the node carries. Issue #666 shows someone already pointing provider: openai at a host that is not OpenAI through a custom BASE_URL under /v1, and the MiniMax provider in pull #594 arrives with its own key variable beside it.
A host that settles every call has no key to give. BlockRun is OpenAI-compatible and covers chat, image, video, music, speech and sound effects from one base URL, and each call is paid for on its own in USDC over x402 on Base or Solana, so there is no key to hold, no account to create and no balance to fund before a run. https://blockrun.ai
Is that a job for the openai slot, or does the provider layer expect a credential on every call? I can put together whatever fits, a provider entry or a short note next to the base_url example, and it is fine to tell me a keyless host is out of scope.
- 主要语言
- Python
- 星标
- 34.3k
- 派生
- 4.3k
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
我们还没有检查这个项目的环境配置文件。先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
OpenBMB/ChatDev 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 76/100
-
难度 1/5 1-3 小时 新手友好度 78/100
-
难度 1/5 1 小时以内 新手友好度 85/100
-
难度 3/5 1-2 天 新手友好度 72/100
-
难度 4/5 3-5 天 新手友好度 35/100
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 84/100
PedestrianDynamics/pyFDS-Evac#343 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 88/100
theskumar/python-dotenv#708 ·
-
难度 1/5 1 小时以内 新手友好度 88/100
维护者通常 2 天内回复
-
Docs Timedelta
难度 2/5 1-3 小时 新手友好度 72/100
pandas-dev/pandas#69919 ·
维护者通常 1 天内回复
-
API documentation
难度 2/5 1-3 小时 新手友好度 72/100
zephyrproject-rtos/west#1009 · 2 条评论 ·
维护者通常 3 天内回复