Feature Request: Support Multiple Accounts per Integration and Bot
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 35/100
- Issue 類型
- 功能
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- typescript
研究方向
Start by locating how integrations are connected, how credentials and permissions are stored, and how Bots receive tools or account access. Trace one integration through connection, Bot assignment, and task execution to see which parts assume a single account. Done means users can connect multiple accounts, assign and manage them per Bot, and use assigned accounts together in a workflow.
由索引模型根據 Issue 內容生成。
描述
Problem
Currently, OpenBot does not provide a clear way to connect multiple accounts of the same integration and assign them to a single Bot.
For example, I want my Chief of Staff Bot to access multiple Gmail accounts, multiple Google Calendar accounts, and potentially multiple accounts from other supported integrations.
A single integration connection should not be limited to one account per user or Bot.
Expected Behavior
Support multiple accounts at different levels:
-
User Level: Allow users to connect multiple accounts of the same integration (e.g., multiple Gmail and Google Calendar accounts).
-
Integration Level: Maintain independent connections, credentials, and permissions for each account.
-
Bot Level: Allow users to assign one or more connected accounts to individual Bots. Different Bots can have access to different accounts.
-
Execution Level: When a Bot performs a task, it should be able to access all accounts assigned to it and use them together in a single workflow.
-
Permission Level: Allow users to independently manage, revoke, and modify account access for each Bot.
Example Use Case
I have a Chief of Staff Bot.
I assign it:
- Gmail: Personal, Work, Business.
- Google Calendar: Personal, Work, Business.
When instructed to prepare my daily briefing, the Bot should retrieve and consolidate relevant information across all assigned accounts into one response.
Goal: Enable multi-account, multi-integration access with flexible account assignment and permissions at the Bot level, rather than treating each integration as a single-account connection.
- 主要語言
- TypeScript
- 星號
- 9.2k
- 分支
- 1.2k
- 平均合併
- 1 天 17 小時
- 30 天內合併 PR
- 173
環境準備
- 提供 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 沒有貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
CopilotKit/OpenBot 的其他 Issue
-
Composio plugin sends x-api-key, but connect.composio.dev/mcp requires x-consumer-api-key可能已有人在做 @azmi2409 於 9 天前認領。 未關閉
難度 2/5 1-3 小時 新手友好度 78/100
CopilotKit/OpenBot#817 · 2 則留言 ·
維護者通常 1 天內回覆
-
Wrong key location at startup可能重新可做 關聯的 PR 已關閉且未合併。 未關閉
難度 1/5 1 小時以內 新手友好度 68/100
CopilotKit/OpenBot#800 ·
維護者通常 1 天內回覆
-
難度 4/5 3-5 天 新手友好度 38/100
CopilotKit/OpenBot#988 · 1 則留言 ·
維護者通常 1 天內回覆
-
壓縮上下文失敗。未關閉
難度 4/5 3-5 天 新手友好度 15/100
CopilotKit/OpenBot#983 ·
維護者通常 1 天內回覆
-
55未關閉
難度 5/5 一週以上 新手友好度 10/100
CopilotKit/OpenBot#975 · 1 則留言 ·
維護者通常 1 天內回覆
查看 CopilotKit/OpenBot 的全部 Issue
相似的 Issue
-
bug
難度 2/5 1-3 小時 新手友好度 65/100
shoelace-style/webawesome#2979 ·
維護者通常 1 天內回覆
-
Chip source filter and denial markers miss Storage rows when a Storage activity source is picked未關閉bug
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 74/100
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 73/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 77/100
omdsh-dev/DSH-better-sidebar#1141 ·
維護者通常 2 天內回覆