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

Offen
#53 3 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
18/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
rust, tauri

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.
Vorherrschende Sprache
Rust
Sterne
3
Forks
1
Ø Merge
9 Std. 51 Min.
Gemergte PRs (30 T.)
310

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus codeatlasdev/atlas

Alle Issues in codeatlasdev/atlas

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.