Settings
Settings is the control panel for the app and this device: appearance and timezone, account and license, backups and recovery, model usage, agent behavior, privacy controls, and native or local-service credentials. Catalog-backed third-party services are governed in the separate Connections Studio.
Preferences here; external authority in Connections. Settings owns how Zimac itself behaves and the integrations implemented directly by the local app. Connections owns manifest-backed providers, their action scopes, one-time approvals and private activity history.
⚙ General & device
Appearance, timezone, setup re-entry and device-specific behavior.
⚙ Account & security
Sign-in, license, backups, recovery keys and deliberate deletion controls.
⚙ Model & team
Inspect usage, change the model connection and tune agent autonomy or roster.
⚙ Native connections
Configure and test services that run through Zimac's local integration layer.
/settings, click the gear, or press ⌘, on Mac. Use the search field to find a preference or native connection.What it is#
Settings is divided into General, Account & security, Model & usage, Agents, and grouped native-connection categories for engineering, cloud, knowledge and communications. General contains appearance and the timezone Zimac uses for “today,” reminders, scheduling and calendar events.
Account & security#
This page covers Zimac organization sign-in, license or subscription status, and device setup. Set up again re-enters onboarding; Start fresh clears the model connection and returns this device to setup while leaving notes, memories and integrations in place.
Security controls include integrity-checked local backups, manual backup and restore, and an exportable passphrase-protected recovery code for encrypted memories. Privacy actions distinguish Erase personal memory from Erase all local data; the latter also removes backups, plugins, pairing, setup, activation and stored credentials and requires deliberate confirmation.
Model & agents#
Model & usage shows the active AI connection and its usage or budget information. Agents controls background thinking, including how readily Zimac speaks up, and organic absorption of durable facts after a conversation. Absorbed items leave a receipt so you can undo them, and dismissals teach the system what not to keep.
The same page manages the specialist roster. Sage always leads; you can bench specialists so Sage stops routing to them or add a specialist for your own stack.
Settings vs Connections#
Some services are implemented as native or local integrations and remain in Settings — including calendar, communication, engineering and cloud controls that depend on this app's local bridges or credential formats. Their cards show connection state, setup instructions and a test or sign-in action.
Manifest-backed third-party providers open in the Connections Studio instead. Connections is the authoritative place to choose allowed actions, approve a high-impact request once and inspect private connection activity. If a command such as “connect Notion” opens Connections rather than Settings, that is expected.
Credentials & storage#
A connection may use a browser sign-in or a key, depending on the provider. Secret values are write-only from the interface: the app returns masked previews rather than the credential itself. Zimac uses macOS Keychain or Windows Credential Manager when available; otherwise secrets use the owner-only local keys.zdata fallback, protected when at-rest sealing is active. If no key location is writable, sealing is unavailable. Test Connection verifies the live configuration without revealing the secret.
Search & shortcuts#
Settings remembers the last category you opened. Press ⌘F on Mac or Ctrl+F on Windows while the panel is open to search static settings and native integrations, and Escape to close. Commands and cards may deep-link to a specific setup screen; manifest-backed IDs are handed off to Connections automatically.