Skip to content

fix(app): say desktop tools off still leaves shell with Ace's macOS permissions - #380

Merged
iamnbutler merged 2 commits into
mainfrom
desktop-wording
Oct 15, 2026
Merged

iamnbutler merged 2 commits into
mainfrom
desktop-wording

Conversation

@iamnbutler

Copy link
Copy Markdown
Contributor

Refs #379

Wording only. The Channel desktop tools tooltip and the sharing prompt now say plainly that turning desktop tools off refuses new desktop calls only: shell commands keep Ace's macOS permissions, such as Screen Recording, so the toggle isn't a security boundary. docs/architecture.md and docs/desktop-tools.md say the same.

The other option in #379 — running shell tools in a process without Ace's TCC grants — awaits a product decision, so the issue stays open.

Verified with bun types, bun run ci, and by rendering the tooltip and sharing dialog in headless Chromium against a source host on a separate port and data dir.

Built in Ace

No — built with Claude Code outside Ace by an overnight issue watcher, because this Mac's Ace Canary is a participant in the running two-person study (#218); dogfooding gap tracked in #5.

…ermissions

The Channel desktop tools description and the sharing prompt read like a capability
boundary, but shell commands inherit Ace's TCC grants (e.g. Screen Recording), so
`screencapture` works with the toggle off. Docs say the same.

Refs #379

Why: apps/app/src/channel-access.tsx#function ChannelAccess | access copy must not imply the desktop toggle bounds what shell commands can see while they run with Ace's macOS grants
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant