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

オープン
#527 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
rust, tauri

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
Rust
スター
3
フォーク
1
平均マージ
9時間 51分
マージ済み PR(30日)
310

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

codeatlasdev/atlas のほかの issue

codeatlasdev/atlas の issue をすべて見る

似ている issue

Rust の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。