Local, cloud, and SSH agent monitoring: privacy and permissions
Agent Control combines status from different places, but the data path and permissions depend on the connector. Local observation, cloud status, and SSH polling are separate workflows.
Local agent sessions
Local connectors read supported status or session metadata from the Mac. The app does not claim that every provider exposes complete transcripts. Some features, such as recent Codex question recovery, inspect local session history under the configured source. Codex source names are monitoring labels, not authenticated account identities.
Cloud sessions
Cursor Cloud, Devin, and Codex Cloud can expose remote status through their integrations. Where configured, credentials are stored in macOS Keychain. Remote handoff opens the provider’s web destination when available. A remote agent’s process ID is not checked against local Mac processes.
SSH hosts
SSH monitoring uses non-interactive batch mode and read-only polling. It does not send commands to approve a remote action. An SSH link is a handoff to the remote environment. Unchanged remote state does not make old activity fresh again.
macOS permissions
Opening a local terminal session can prompt for Automation access. Sending a verified native terminal menu choice requires explicit terminal-control opt-in and Accessibility access. The app checks the exact target and reports when permissions or targeting are unavailable; it keeps the request pending rather than pretending the action succeeded.
Practical privacy review
- Enable only the connectors you want monitored.
- Review what a cloud provider API exposes before storing its credential.
- Keep local session-history sources limited to the folders you intend to monitor.
- Use the opt-in terminal controls only when their permissions and target checks fit your workflow.
- Prefer observation and handoff when you want the agent to retain all decision-making in its own interface.
Agent Control settings and local observations remain on the Mac; optional API credentials use Keychain. Provider services still apply their own data handling to cloud work. Read the feature page for all connector tiers.