Remote companion: get agent notifications and reply to agents from a phone

Aberta
#53 3 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
18/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
rust, tauri

Direção de pesquisa

This is a design-scale feature spanning hostd, a new web UI, push delivery and token lifecycle, so start by reading the linked public examples (stravu/crystal#89, #26, siteboon/claudecodeui) and the existing hostd request-handling and Settings code in this repo to see what authentication and agent-state plumbing already exists. Sketch the endpoint surface and pairing/revocation flow against the three acceptance criteria before writing anything; the first deliverable is an agreed design, not a patch. Done means all three checkboxes hold, including revocation cutting live sessions immediately.

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

Descrição

area: desktop status: needs-triage type: feature

Problem

Agents run for minutes to hours. When away from the desk, there is no way to know an agent is waiting or to send it a follow-up.

Evidence

From research on parallel-agent desktops and worktree tools, this is a recurring user request:

A recurring request across agent-workspace and parallel-agent tools, with high upvote counts in their public trackers. Public examples: https://github.com/stravu/crystal/issues/89 and https://github.com/stravu/crystal/issues/26; https://github.com/siteboon/claudecodeui (14k ★) exists mainly for this.

Proposed behavior

  • Opt-in remote access to the agent inbox: a small authenticated web UI served by hostd (reachable via Tailscale/WireGuard/SSH tunnel; no Atlas cloud relay).
  • Shows agents and states, pushes needs you / done (Web Push or ntfy), lets you answer approvals and send a follow-up prompt.
  • Pairing by QR code with a scoped token; revoke in Settings.

Acceptance criteria

  • Off by default; enabling shows the URL + QR and the threat model.
  • From a phone: see agent list, approve/deny a pending prompt, send text to an agent.
  • Token revocation cuts active sessions immediately.
Linguagem predominante
Rust
Estrelas
3
Forks
1
Merge médio
9h 51min
PRs com merge (30d)
310

Preparar o ambiente

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 codeatlasdev/atlas

Todas as issues de codeatlasdev/atlas

Issues semelhantes

Mais issues de Rust

Receba novas issues na sua caixa de entrada

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