Proposal: OrcaRouter as an optional model provider for OpenTag
維護者通常 10 天內回覆
還沒有人認領這個 Issue。
評估
研究方向
從 agent/agent.py 開始，該檔案會根據環境變數設定 ChatOpenAI，並檢查 use_responses_api=True 如何影響目前的模型設定。在實作之前，釐清選用的 provider 設定與相容性預期；實作應保留 OpenAI 預設值與現有的環境變數契約，同時加入經過測試的 provider 選擇。
由索引模型根據 Issue 內容生成。
描述
OpenTag is a refreshingly concrete thing to ship: a self-hosted, deployable knowledge-work agent that does the work where the team already is — in the Slack or Teams thread. I particularly like the human-in-the-loop design, where a Linear or Notion write pauses behind an approval gate and research comes back as a cited brief with a chart inline, so the bot feels like a careful colleague rather than a firehose.
Because OpenTag is built to be forked and pointed at your own agent, the model behind it is a real decision for each adopting team. Today agent/agent.py wires a single OpenAI model from OPENAI_API_KEY and OPENAI_MODEL; forks may want to pick which model handles routine triage versus deep research without rewriting the graph.
I'd like to propose adding OrcaRouter as an optional provider for OpenTag — an additional choice, not a replacement; the OpenAI default and the env-var contract stay as they are. OrcaRouter exposes an OpenAI-compatible API and uses standard API-key authentication. For a fork-and-ship project like this, the useful parts are: many chat and reasoning models behind one endpoint, so a cheap/fast model can handle routine triage while a reasoning model does deep research without changing the graph; automatic routing with provider failover, which matters for an on-call bot where an outage should not silently drop a Slack mention; and usage tracking with per-team budgets when a whole workspace shares one bot.
Where it would plug in: agent/agent.py builds its model through LangChain's ChatOpenAI entirely from environment variables, so an OrcaRouter option would most plausibly be an optional model/base-URL configuration beside OPENAI_API_KEY. The agent currently targets the OpenAI Responses API (use_responses_api=True); how an OpenAI-compatible provider slot should fit that is exactly what I'd want your opinion on before writing anything — nothing here is implemented or tested.
OrcaRouter is also appearing across the open-source ecosystem — projects such as RAGFlow, Dify, and NocoBase integrate with it (see https://www.orcarouter.ai/built-with). One transparency note: OrcaRouter runs an optional open-source partner program under which approved projects can receive a 5% revenue share from usage attributed to their integration. Participation is not a prerequisite for integrating, and I'd happily follow any disclosure or governance rules this repo prefers.
I'm an engineer on the OrcaRouter team. If maintainers think an optional provider slot fits OpenTag's goals, I'd be glad to submit an implementation PR for review; if not, I'd still welcome your thoughts. Thanks for building something teams can actually fork and ship.
- 主要語言
- Python
- 星號
- 1.3k
- 分支
- 138
- 平均合併
- 5 天 10 小時
- 30 天內合併 PR
- 7
環境準備
這個專案沒有提供開發容器、Dockerfile 或貢獻指南，環境需要你自己搭建：先看它的 README，通用步驟見我們的新手貢獻指南。
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
CopilotKit/OpenTag 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 88/100
CopilotKit/OpenTag#86 ·
維護者通常 10 天內回覆
-
Approval card shows Python repr for list arguments that contain objects可能已有人在做 @RaphaelFakhri 於 9 天前認領。 未關閉
難度 2/5 1-3 小時 新手友好度 25/100
CopilotKit/OpenTag#90 ·
維護者通常 10 天內回覆
-
難度 5/5 一週以上 新手友好度 25/100
CopilotKit/OpenTag#76 ·
維護者通常 10 天內回覆
-
難度 5/5 一週以上 新手友好度 35/100
CopilotKit/OpenTag#72 ·
維護者通常 10 天內回覆
-
難度 5/5 一週以上 新手友好度 25/100
CopilotKit/OpenTag#36 ·
維護者通常 10 天內回覆
查看 CopilotKit/OpenTag 的全部 Issue
相似的 Issue
-
enhancement help wanted
難度 2/5 1-3 小時 新手友好度 76/100
Git-Hospital/githealthcheck#61 ·
維護者通常 1 天內回覆
-
changelog investigate
難度 2/5 1-3 小時 新手友好度 67/100
ramnes/notion-sdk-py#433 ·
-
Partial method descriptors raise on class access可能已有人在做 @Gambit-Checkmate 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 76/100
維護者通常 19 天內回覆
-
docs pkg:core
難度 1/5 1 小時以內 新手友好度 84/100
pydantic/pydantic-ai#11929 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
intake/intake-esm#789 ·