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

Abierto
#53 3 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
18/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust, tauri

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
Rust
Estrellas
3
Forks
1
Merge medio
9 h 51 min
PR fusionados (30 d)
310

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de codeatlasdev/atlas

Todos los issues de codeatlasdev/atlas

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.