Security model

How the desktop app keeps you in control.

  • Human approvals — write/exec tools never auto-approve; no --dangerously-skip-permissions. Codex uses workspace-write + on-request approval policy.
  • Local files — tracker, archives, and profile stay on disk in your workspace.
  • No stored credentials — provider / Gmail / Notion auth remains in the provider CLIs and connectors. No API keys in SQLite.
  • Safe process spawn — argv vectors only; untrusted text reaches the provider as message content.
  • Path guards — workspace joins reject .. and absolute escapes.
  • Destructive resets — /reset needs confirmation in the app and again upstream (Claude only).
  • No telemetry backend — network use is your AI provider and what upstream workflows fetch.
  • Honest submission semantics — preparing documents never marks an application as submitted to an employer.
Profile is personal data. Don't push your workspace profile to a public fork. Upstream gitignores tracker and tailored application archives.