Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Validate desktop tool use in Ace and track known gaps

オープン
  • 何か問題がありますか？
#427 コメント 2 件 リアクション 0 件 担当者 0 名 GitHub で見る

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

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
8/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
macos, typescript
領域
desktop-dev, testing

調査の方向性

This is a tracking issue for validating desktop tools in a signed Canary, not a single change. The one open check is the sharing path: a teammate's invocation with sharing on should reach desktop tools as the owner allowed, and with sharing off it should be refused. The upstream engine and its gaps live in githubnext/desktop-tools, so start with native/patches/README.md there for the Peekaboo patch state. Done means every check passes in a Canary with a real provider run and each gap is fixed or accepted.

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

説明

Validate the desktop tools as Ace ships them, and keep the known gaps in one place. The engine and its roadmap live in githubnext/desktop-tools (the former meta is githubnext/desktop-tools#11). This issue covers only what Ace owns: the pinned package, the channel setting, sharing, and the agent's experience in real runs.

Done when: every check below has passed in a signed Canary with a real provider run, with that Canary's version noted, and every gap is fixed or explicitly accepted.

Validation

  • An agent drives TextEdit, then screenshots and reads its window. The screenshots stream to a teammate. (Study scenario 20, 0.0.36.)
  • The agent fills a Save sheet's name, picks a folder and saves (#378 via githubnext/ace#382 and desktop-tools#8, 20b, 0.0.38).
  • desktop_insert types into a Save sheet's filename field (#390 via githubnext/ace#402 and desktop-tools#9, 20c).
  • Turning desktop tools off refuses every desktop_* call. The refusal is clear, and turning them back on works without restarting the channel. (Study D2, 0.0.46.50.)
  • A teammate's invocation with sharing on reaches desktop tools as the owner allowed. With sharing off it is refused. The sharing text matches what happens.
  • Stopping a run, or losing the connection, during a desktop action settles it as completed, refused or unknown, and the action isn't replayed after the worker reopens. (Study D3b/D3c, 0.0.46.50.)
  • Two channels with desktop tools on at the same time don't act on each other's targets. (Study D4 and R1, 0.0.46.51 and .52. Agents can't yet tell whose new window is whose: githubnext/desktop-tools#17.)
  • Peekaboo patch tests pass at the pinned commit (desktop-tools#10, Ace githubnext/ace#425). Every pin bump re-runs them. (8801b31 in full; 4618b33 adds one bridge patch, and its bridge tests pass.)

Known gaps

  • Shell capture: with desktop tools off, the shell can still capture the screen with Ace's macOS permissions. Isolating that is not planned (#379). The wording in githubnext/ace#380 and githubnext/ace#389 documents it.
  • Background key presses: desktop_key can't verify a background Cmd+W. The recovery hint suggests --foreground, which the tool doesn't expose (githubnext/desktop-tools#11, comment from October 7).
  • Engine gaps, tracked in desktop-tools:
    • focus and paste in WebKit (githubnext/desktop-tools#5);
    • temporary clipboard paste (githubnext/desktop-tools#3);
    • pointer delivery and multiple displays (githubnext/desktop-tools#2);
    • Chrome's Accessibility titles (githubnext/desktop-tools#6);
    • why inspection is unavailable (githubnext/desktop-tools#1);
    • window, menu and dialog workflows, including Ace's own Open Folder picker (githubnext/desktop-tools#4);
    • patch drift in dev builds (githubnext/desktop-tools#7).
  • Not available everywhere: cloud compute channels have no desktop, so their toggle is hidden (#422). Hosted channels use the workspace host's desktop. Operating a teammate's desktop is deferred (#202).
  • Upstream test failures: two Peekaboo tests fail on unpatched 4.8.0 as well (native/patches/README.md in desktop-tools).

Tracked by githubnext/ace#5.

主要言語
TypeScript
スター
1
フォーク
0
30日以内にマージされた PR はありません

環境構築

  • Dockerfile・Docker Compose ファイルなし
  • プルリクエストのテンプレートあり
  • コントリビューションガイドなし

はじめの一歩

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

githubnext/ace2 のほかの issue

githubnext/ace2 の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

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

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