Teach how Ace works and what sharing exposes on first run
まだ誰も着手していません。
評価
- 難易度
- 3/5
- 見積もり時間
- 1〜2日
- 初心者へのやさしさ
- 35/100
- issue の種類
- 機能追加
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- typescript
調査の方向性
The payload names no source files, so start with docs/terms.md for the vocabulary and the README to see how the product is described now. Find the existing first-run and the sharing, channel and project controls in the app. The checklist defines what the copy must cover. Related work is #214 (the collaborator-invocation toggle) and #162 (non-Git folders), so check those before writing. Done means each checklist item appears in a short first-run sheet or inline on its control, in terms.md vocabulary.
索引モデルが issue の本文から書いたものです。
説明
New users don't know how Ace works or what sharing exposes. Teach it in the product, not only in the README: a short first-run sheet plus inline copy on the controls, not a tour. Use the terms vocabulary.
Already done
- Sharing toggle states what it grants (#243, #389): "Teammates can run commands as you on this machine, with Ace's macOS permissions such as Screen Recording." Cloud compute channels name the container instead (#422). Verified in study scenario 6.
- Desktop tools toggle: its tooltip names owner and collaborator runs, and turning it off says shell still has Ace's macOS permissions (#380). A refused call tells the agent to ask the owner (#258).
- Non-Git folders (#162): Cmd+O offers
git initand explains that lanes are Git worktrees (#222,apps/app/src/open-project.tsx). - Where a channel lives is shown in channel details: Host, Hosted plus Workspace, or the cloud container (
apps/app/src/placement.ts,channel.tsx, #422).
Remaining
- First-run sheet that covers each of these in a line:
- Your machine is the host. Channels and agents run on this Mac as you. Lanes are Git worktrees, not sandboxes.
- Your tailnet is your team. Everyone on the tailnet running Ace can see your channels and their history. There are no Ace accounts or invitations. This was the least understood rule in the study (1/3, scenario 1).
- Sharing gives teammates your machine. Teammates can invoke agents only when you turn agent access on. Desktop tools are a separate owner toggle.
- Where a channel lives: local, a teammate's host, hosted, or cloud compute.
- Projects vs. channels: Cmd+O adds a project; creating a channel is a separate action.
- Say on the channel, or near the channel list, that tailnet teammates can see it. No in-app copy says this today.
- Say that only the owner controls agent access and desktop tools, instead of leaving people to infer it from a disabled control (scenario 1).
- Decide whether turning desktop tools on gets a confirmation like agent access does (scenario 7).
- Re-run the scenario 1 explain-back after this ships. The baseline on 0.0.26 was 1/3 for visibility and 2/3 for everything else.
Part of #217's pre-Universe list.
- 主要言語
- TypeScript
- スター
- 1
- フォーク
- 0
- PR マージ指標
- 30日以内にマージされた PR はありません
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドなし
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
githubnext/ace2 のほかの issue
-
難易度 1/5 1時間未満 初心者へのやさしさ 94/100
githubnext/ace2#487 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 90/100
githubnext/ace2#486 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 67/100
githubnext/ace2#459 ·
-
難易度 1/5 1時間未満 初心者へのやさしさ 88/100
githubnext/ace2#437 ·
-
難易度 4/5 3〜5日 初心者へのやさしさ 35/100
githubnext/ace2#442 ·
githubnext/ace2 の issue をすべて見る
似ている issue
-
bug priority: P2
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 73/100
mattermost/compass-design#106 ·
メンテナーはふだん 1 日以内に返信
-
clawsweeper:needs-maintainer-review clawsweeper:needs-product-decision clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:other issue-rating: 🦞 diamond lobster P2
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
openclaw/openclaw#176671 · コメント 1 件 · リアクション 1 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 66/100
nordcraftengine/nordcraft#1400 ·
メンテナーはふだん 1 日以内に返信