crew: one-click bypass-permissions mode and a voice mode (dictate tasks, spoken replies)

Aperta
#527 0 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
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust, tauri

Direzione di ricerca

Start by reading how crew tool approvals are configured and enforced, then trace the chat composer and Telegram voice-message handling on desktop and mobile. The issue names no files or tests, and covers two broad features with several optional behaviors. Done means both modes work across the described clients while preserving the stated safety rules and making bypass state visible.

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

Descrizione

area: desktop status: needs-triage type: feature

Problem

Using Atlas Crew day to day, the per-tool-call approval prompts get in the way. Every file edit or command waits for someone to click Allow, so a crewmate cannot just work through a task. There is also no way to talk to a crewmate: every task has to be typed.

Suggestion 1: a visible "bypass permissions" mode

The protocol already has approval: "auto" (allow all without prompting), but it is not something a user finds or flips quickly while working. Proposal:

  • A toggle in the crewmate's chat (Desktop and Mobile): Ask / Bypass (auto), switchable at any time and applied to the next tool call, without opening the settings window.
  • A crew-wide default in crew settings, so new crewmates start in the mode the owner prefers.
  • Clear state: a badge on the crewmate and its thread while it runs in bypass, so it is always obvious which crewmates act without asking.
  • Keep the existing safety rules as they are: GitHub and webhook tasks still ask unless the automation sets allow_auto, every tool call is still in the audit log, and Pause all still stops everything.

Suggestion 2: voice mode

  • Dictate a task: a mic button (push-to-talk) in the composer on Desktop and Mobile, and accept Telegram voice messages, transcribed into the task prompt so it can be checked before sending.
  • Optional spoken replies: read the crewmate's short reply out loud, for hands-free use from the phone.
  • Voice answers to cards (optional): answer approval and choice cards by voice (allow, deny, pick an option).

Why

Crew is meant to run agents unattended. Fewer interruptions (bypass) and a faster way to send work (voice) make it practical from the phone, away from the computer.

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.