ZODConsent before privileged operations
File operations should remain inside an approved project. Browser and desktop control require separate user approval and any macOS security prompts. No universal shell or remote access is granted merely because a user connects an MCP tunnel.
What a trustworthy result includes
- Which tool ran, on which approved project and why.
- Files and version hashes before and after a change.
- Test outcomes including failures.
- A documented recovery or rollback path.
- Clear errors when a tool or AI account lacks permission.
Connections, accounts and costs
MCP is the transport layer—it does not guarantee ChatGPT Free accounts have write-enabled custom MCP permissions. Provider plan limits still apply. We do not intend to require a separate pay-per-token API key or force a large local model on Community users.
Not a completed security audit: the installed Mac project source has passed isolated hardening tests, but live gateway integration, independent Mac acceptance and a public distribution security review remain incomplete.
Local first—not a promise that no data leaves your device
Projects are designed to be stored locally. A ChatGPT request or optional online service may transmit information to its own provider according to that provider's terms and the permissions you grant. We will document these data flows before releasing software to the public.
Early unsigned app builds
They may trigger macOS security warnings. We will not ask users to turn off Gatekeeper globally, disable security monitoring or run opaque scripts. Beta assets must have published hashes and release notes.