Feature request: let one OpenBot instance act on my other machines through their own OpenBot installs

Aberta
  • Algo errado?
#942 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
8/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
typescript
Domínio
authorization, backend

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
TypeScript
Estrelas
9.2k
Forks
1.2k
Merge médio
2d 20min
PRs com merge (30d)
135

Preparar o ambiente

  • Inclui um Dockerfile ou arquivo Docker Compose
  • Tem um modelo de pull request
  • Sem guia de contribuição

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de CopilotKit/OpenBot

Todas as issues de CopilotKit/OpenBot

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.