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 于 8 天前认领。 未关闭
难度 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 天内回复
-
壓縮上下文失敗。未关闭
难度 4/5 3-5 天 新手友好度 15/100
CopilotKit/OpenBot#983 ·
维护者通常 1 天内回复
-
55未关闭
难度 5/5 一周以上 新手友好度 10/100
CopilotKit/OpenBot#975 · 1 条评论 ·
维护者通常 1 天内回复
查看 CopilotKit/OpenBot 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 83/100
appandflow/stim#5258 ·
维护者通常 1 天内回复
-
area/docs framework/hugo help wanted language/markdown
难度 1/5 1 小时以内 新手友好度 88/100
维护者通常 1 天内回复
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
难度 1/5 1 小时以内 新手友好度 68/100
lingdojo/kana-dojo#33660 · 1 条评论 · 5 个 reaction ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
drizzle-team/drizzle-orm#6639 ·
维护者通常 4 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 76/100