Feature request: let one OpenBot instance act on my other machines through their own OpenBot installs
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 8/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- typescript
- 领域
- authorization, backend
调研方向
This is design work, not a code change, and the payload names no files, tests or entry points. Start with the related issues #648 (phone pairing for approvals) and #871 (one computer per person) to see what pairing and per-user constraints already exist. Done means an agreed design for outbound machine pairing, per-machine permissions and machine-tagged event logging, not a patch.
由索引模型根据 Issue 内容生成。
描述
What I'd like
I run OpenBot on a server and also have it installed on two laptops. I want to talk to the server instance (e.g. from my phone) and have that bot run actions on my laptops through the OpenBot apps already installed there: shell commands, files, local apps. Same conversation, memory and routines, and the bot picks which machine to act on ("on my work laptop, check X").
Grok Bot works like this today: one bot, with several of my registered computers it can act on, and each action approved per machine.
Why
A lot of real work lives on my laptops: local files, installed apps, a corporate machine I can't move to the server. Right now each install is a separate island, so the server bot can't reach them.
Rough shape
- Pair an OpenBot install on a laptop with a main instance. The laptop connects outbound, so no inbound ports or SSH.
- The main bot sees the paired machines and can run tools on them.
- Per-machine permissions and approval rules (e.g. some paths or actions always blocked on a work laptop).
- The event log shows which machine each action ran on.
Related
#648 (phone pairing for approvals) and #871 (one computer per person) are close, but neither covers acting on the user's own machines.
Is this on the roadmap? It's the deciding factor for me in moving my setup to OpenBot.
- 主要语言
- TypeScript
- 星标
- 9.2k
- 派生
- 1.2k
- 平均合并
- 2 天 20 分钟
- 30 天内合并 PR
- 135
环境准备
- 提供 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 于 6 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
CopilotKit/OpenBot#817 · 2 条评论 ·
维护者通常 1 天内回复
-
Wrong key location at startup可能已有人在做 @charan-rathore 于 16 天前认领。 未关闭
难度 1/5 1 小时以内 新手友好度 68/100
CopilotKit/OpenBot#800 ·
维护者通常 1 天内回复
-
The Bot's screen opened full size has no visible way to close it可能已有人在做 @NathanTarbert 今天认领。 未关闭
CopilotKit/OpenBot#953 · 已指派 1 人 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 15/100
CopilotKit/OpenBot#937 ·
维护者通常 1 天内回复
-
难度 3/5 1-3 小时 新手友好度 25/100
CopilotKit/OpenBot#936 ·
维护者通常 1 天内回复
查看 CopilotKit/OpenBot 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 84/100
pingdotgg/t3code#30228 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
-
ci-cd desktop size:low telemetry-improvement telemetry-round-1
难度 2/5 1-3 小时 新手友好度 66/100
vfarcic/dot-agent-deck#2079 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 83/100
维护者通常 1 天内回复