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

Aperta
#53 3 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
18/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust, tauri

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.
Lingua principale
Rust
Stelle
3
Fork
1
Merge medio
9h 51m
PR unite (30g)
310

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di codeatlasdev/atlas

Tutte le issue di codeatlasdev/atlas

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.