Skip to main content
Access has several interfaces to the same local service. Choose one for the person or agent doing the work; its credential and permissions still matter. Agent profiles are used by CLI and MCP. Human profiles are used by the iOS app and Mobile API. See Profiles and permissions.

​
Background service and closing the app

The Mac app uses a separate background core for tool calls and enabled HTTP listeners. You can close its window while the app remains running. Closing the window and quitting Access are different. The core stops when its last local client disconnects. A connected local MCP stdio client can keep it running after the Mac app quits; an HTTP or iPhone client alone does not. For dependable MCP HTTP or Mobile API access, leave the Mac app running and the Mac awake. It does not need to stay in the foreground. CLI commands and local MCP stdio clients can start the core on demand. This does not make Access an always-on server that survives logout or shutdown. To block tool access, use the channel switches or revoke the relevant credential in Access. Closing the app window is not a way to revoke permissions.