Choose permissions deliberately
Understand which access a feature needs, who grants it, and how to inspect or change it.
Grant access when you want to use the feature that needs it. Push settings, macOS permissions, workspace roles and tool approvals are separate choices.
On the Mac
Use Settings → Permissions to inspect available grants and follow a control to System Settings when macOS owns the permission.
| Access | What it enables | When it matters |
|---|---|---|
| Microphone | Recording your voice or an in-person meeting. | When you choose a recording or voice feature. |
| System audio | Capturing the other side of a meeting call. | When you enable call-audio capture. |
| Calendar | Using this Mac's calendar for supported meeting context and calendar features. | When you choose a local calendar feature. |
| Contacts | Looking up a person's available contact details. | When you request a contact-based task. |
| Reminders | Supported tasks involving this Mac's Apple Reminders. | When you enable and request that feature. |
| Messages and Full Disk Access | Reading supported local Messages data. Full Disk Access is a separate macOS grant required for that source. | Only when you choose to use Messages access. |
| Automation for Messages | Supported sending through the Mac's Messages app. | A separate choice from reading history; review the actual recipient and message. |
| Location | Local location-aware features. | When you enable the relevant feature. |
| Notifications | Delivering alerts on this Mac. | When you enable notifications. |
Your installed version and macOS determine the exact available controls. Inspect the current state without prompting from a shell:
push permission statusThe CLI can explain manual setup. It cannot grant OS access for you. An operating-system permission also does not authorize an agent to send a message, delete a reminder or disclose content without your instruction.
Data Access and workspace access
File access and file publishing are human-owned controls in workspace settings. Workspace roles separately decide who can file work, run agents, watch terminals or control them. Granting one does not automatically grant the others.
A coding agent runs in the host's environment and uses its available files and tools. Treat terminal control and unattended permission modes accordingly. A role is not an operating-system sandbox around the agent.
Local source access happens on your Mac. Downstream use by an agent or a configured provider can still send relevant context for processing; see data handling.
On the iPhone
Microphone access supports voice capture. Notifications support alerts and Live Activities. Photo or location access is used only for features you choose that attach that context to captures. Review both Push settings and iOS Settings when changing access.
Ordinary account-based connection to a discovered Mac does not require scanning a camera pairing code. The phone's permissions are separate from the host Mac's grants.
Change or remove access
Review the feature in Push, then revoke its OS grant in System Settings if needed. Disconnect devices and remove workspace access independently. Review existing public links separately; revoking a local microphone grant does not remove a published file.
Before uninstalling or deleting local data, back up what you need, check that phone captures synced, and read account deletion consequences.