Grace won’t start
Check macOS Gatekeeper. Open System Settings → Privacy & Security and allow Grace once after the first blocked launch.
Clear help for Grace on Mac, the iOS companion, local models, connectivity and everyday workspace issues.
Check macOS Gatekeeper. Open System Settings → Privacy & Security and allow Grace once after the first blocked launch.
Close inactive chats, inspect local model load and provider limits, then use stricter execution settings for demanding workflows.
Confirm that the corresponding CLI is installed and available on your Mac. Restart Grace so discovery can run again.
Check that the local runtime is running, the selected model is installed and enough memory is available for the chosen tier.
The companion is distributed through TestFlight during early access. Keep the newest available build installed.
Use the same LAN or Tailscale network, keep Grace running on the Mac and select the available workspace in the app.
Check Grace notification permissions in iOS Settings and confirm that the Mac workspace can reach the companion.
Use Tailscale for a private connection between your iPhone and Mac without exposing the Grace server publicly.
Use Time Machine or a manual backup routine for the Grace workspace and project folders containing chats, runs and local state.
Local work stays on your Mac. External agents and providers may process the prompts you send to them; Grace makes that distinction visible.
Restore the workspace data and reconnect the installed agents. Provider authentication may need to be completed again.
Open Live Activity, stop or pause the turn, inspect pending approvals and restart only the affected step where possible.
Send the device, Grace version, affected agent and a short description of what happened. Screenshots help.
Contact support ↗