Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Ship a signed Desktop Tools app for agents outside Ace

Geschlossen
  • Stimmt etwas nicht?
#27 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
15/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
github-actions, swift, typescript
Bereich
ci-cd, cli, desktop

Rechercherichtung

Start with src/app.ts and the existing runtime start call, then read Ace's apps/desktop/src/native.ts and apps/desktop/scripts/sign.ts for the signing order. The work spans a new menu bar app target, the MCP defaults in desktop-tools-mcp, and .github/workflows/release.yml, and it needs Apple signing secrets from an admin. Done means a signed, notarized build that passes codesign --verify --deep --strict and spctl --assess, plus a working MCP setup in Claude Code and Codex.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

enhancement

Agents outside Ace (Claude Code, Codex) can use desktop tools today only by borrowing Ace's grants through its client and socket (#24, stretch notes on #12). A standalone signed host app gives them their own visible, revocable grants and leaves Ace's alone.

This reverses the README's "a vendor-signed companion is not part of this package"; the README changes with it.

Shape

App: Desktop Tools.app, bundle ID dev.githubnext.desktop-tools, team 8S43JJMN6B.

  • It's a menu bar app (LSUIElement) whose process loads the runtime (libDesktopTools.dylib) and calls desktop_tools_start(socket, "dev.githubnext.desktop-tools.desktop-client"), exactly like Ace (ace apps/desktop/src/native.ts).
  • The client ships as Contents/MacOS/desktop-tools-client, signed with identifier dev.githubnext.desktop-tools.desktop-client.
  • Socket: ~/.local/state/desktop-tools/desktop.sock (0600). Client link: ~/.local/state/desktop-tools/desktop-client.

The menu shows:

  • Accessibility, Screen Recording and Keyboard input status, with grant buttons (desktop_tools_permission).
  • Serving on or off; off stops the runtime.
  • The last action and its caller (the client's parent process name), so outside use is visible. This is the minimum answer to #24 for this app.
  • Quit.

MCP: desktop-tools-mcp (#12) defaults --client and --socket to the app's state dir and --name to "Desktop Tools". Setup becomes:

  • claude mcp add desktop -- npx -y github:githubnext/desktop-tools desktop-tools-mcp
  • or the Codex mcp_servers equivalent.

The tool definitions move into the package so Ace and MCP share one source.

Build and release:

  1. src/app.ts: build the runtime, assemble the bundle, and sign inside-out with the hardened runtime. Copy Ace's apps/desktop/scripts/sign.ts order: Frameworks, client (identifier, no entitlements), executable, app; then codesign --verify --deep --strict.
  2. .github/workflows/release.yml on workflow_dispatch, environment release:
    • temporary keychain from the p12;
    • notarize the zip and DMG with xcrun notarytool and an App Store Connect API key;
    • staple;
    • spctl --assess;
    • attach to a GitHub Release.
  3. No auto-update in v1 (no Sparkle); a release is downloaded by hand.

Secrets: to be added by an admin to environment release, same values as Ace's desktop-* environments.

  • Secrets: DT_CERTIFICATE_P12, DT_CERTIFICATE_PASSWORD, DT_NOTARY_PRIVATE_KEY.
  • Variables: DT_CODESIGN_IDENTITY, DT_NOTARY_KEY_ID, DT_NOTARY_ISSUER.

Order

  1. App target and local signed build (local Developer ID identity), then a live MCP run with Claude Code and Codex.
  2. Release workflow and notarization.
  3. Land #12 rebased, with defaults and shared tool definitions.
  4. README, and a link from Ace's docs.
Vorherrschende Sprache
Swift
Sterne
0
Forks
0
Ø Merge
42 Min.
Gemergte PRs (30 T.)
123

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

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 githubnext/desktop-tools

Alle Issues in githubnext/desktop-tools

Ähnliche Issues

Weitere Issues zu Swift

Neue Issues direkt in Ihr Postfach

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